Built for: “run zsh commands from the macOS menu bar”
Your shell environment, one click away
Run the command with the zsh environment it expects
A command that works in Terminal should not fail in a launcher because PATH, aliases, functions, or a version manager disappeared. Shell Click initializes commands through your account’s interactive login shell.
~/Code/legacy-app
nvm use && npm run dev ~/Code/api
start-local-api ~/Code/app
mise exec -- pnpm dev The problem
GUI launchers often start with the wrong environment
macOS apps do not automatically inherit the same shell setup as Terminal. That difference turns working commands into “command not found,” selects the wrong runtime, or bypasses the alias you depend on.
The Shell Click answer
Launch through the shell you already configured
Shell Click starts the command through your account’s interactive login shell, inside its saved working directory. Your normal PATH, version managers, aliases, and functions remain available.
What stays attached
The command, its context, and its terminal
Login-shell initialization
Start with the environment your Terminal sessions are configured to use.
Aliases and functions
Reuse concise commands already defined in your interactive shell.
Correct project runtimes
Let version managers resolve Node, Python, Ruby, and other tools as expected.
Why it fits
No duplicate environment configuration
Keep shell setup in the place it already belongs. You do not need to copy PATH values into every shortcut or rewrite working aliases as standalone scripts.
Shell Click for macOS
If it runs in your shell, keep it one click away.
Save the working command with its folder and launch it from a native macOS menu-bar popover.