Built for: “better way than four Terminal windows running commands”
One home for long-running commands
Stop rebuilding the same four-terminal setup
Save one shortcut per process, then start each one from the dashboard or menu bar. Every process keeps its own output, controls, working folder, and interactive terminal.
~/Code/laravel-app
npm run dev ~/Code/laravel-app
php artisan reverb:start ~/Code/laravel-app
php artisan queue:work ~/Code/laravel-app
stripe listen --forward-to localhost/webhook The problem
Terminal windows are doing the job of a process dashboard
A typical local stack can need a frontend, queue worker, WebSocket server, and webhook listener. Tabs work until one closes, a command starts in the wrong folder, or you can no longer tell which process owns a port.
The Shell Click answer
Give every process a named, persistent place
Shell Click turns each recurring command into a compact card. Start it, inspect its output, send Control-C, or stop the foreground process group with SIGTERM without hunting through Terminal windows.
What stays attached
The command, its context, and its terminal
No terminal choreography
Start recurring processes from saved cards instead of reopening and arranging windows.
Independent control
Read, interrupt, restart, or stop each process without disturbing the others.
Ports stay findable
Detected listening ports appear with running commands and open in your browser with a click.
Why it fits
tmux reliability without learning a tmux workflow
Shell Click manages isolated tmux sessions behind the interface and bundles tmux with the app. You keep the persistence without building layouts or memorizing key bindings.
Shell Click for macOS
Keep the stack. Lose the terminal sprawl.
Your existing commands stay unchanged; Shell Click makes them easier to start, observe, and return to.