Built for: “terminal manager for multiple projects on macOS”
Project command manager for Mac
Every project command, already in the right folder
Move between projects without looking up commands, repeating cd, or rebuilding a terminal layout. Shell Click remembers the folder and gives every saved command its own persistent session.
~/Code/storefront
pnpm dev ~/Code/api
uv run fastapi dev ~/Code/platform
docker compose up The problem
Project context keeps leaking out of the terminal
The command is only half the setup. You also need the right repository, shell environment, port, and output window. Multiply that by several projects and terminal tabs become a fragile filing system.
The Shell Click answer
Save the project context with the command
Each Shell Click shortcut pairs a command with an explicit working directory. Start a frontend in one repository, a worker in another, and a local database in a third without navigating between folders first.
What stays attached
The command, its context, and its terminal
Folder-bound commands
The working directory is part of the shortcut, so every run starts in the intended project.
Persistent sessions
Long-running work stays attached to a private tmux session even when the app window is elsewhere.
Project status at a glance
See what is running and follow detected localhost ports without inspecting every terminal tab.
Why it fits
A command manager, not a new development environment
Keep your editor, shell, and existing tooling. Shell Click adds a native command dashboard and menu-bar popover around the commands you already trust.
Shell Click for macOS
Switch projects. Keep the context.
Open Shell Click from the menu bar and start the command that belongs to the project in front of you.