Built for: “launch a saved command in a real interactive terminal”
Saved commands without the black box
A command launcher should still feel like a terminal
Shell Click does not fire a command into an invisible background task. It keeps a live terminal attached, so you can read output, answer prompts, debug failures, and continue typing afterward.
~/Code/app
pnpm create vite ~/Code/app
pnpm test --watch ~/Code/api
bin/rails console The problem
Fire-and-forget launchers stop helping when a command talks back
Development commands ask questions, stream logs, display progress, and sometimes need Control-C. Copying a command or running it silently removes the interaction that made Terminal useful.
The Shell Click answer
Save the repetitive part, keep the interactive part
Start with one click, then use the terminal normally before, during, or after the saved command. The session remains in its working directory and keeps its rendered output available.
What stays attached
The command, its context, and its terminal
Type at any time
Keyboard input stays connected to the same working shell before, during, and after launch.
See the whole conversation
Follow output, prompts, errors, and the returned shell without switching applications.
Use familiar controls
Send Control-C directly or stop the foreground process group with SIGTERM.
Why it fits
More than command history
History helps you find old text. Shell Click remembers the command, folder, running state, terminal session, and detected ports as one reusable shortcut.
Shell Click for macOS
One click to start. A full terminal when you need it.
Shell Click removes repeated setup without taking away the shell interaction that solves real problems.