Built for: “open VS Code workspaces from the macOS menu bar”
Project launcher for macOS
Open the project and start its command from one saved shortcut
Pair each repository with the command that opens or runs it. Shell Click starts in the saved folder, so code ., your local server, and follow-up terminal work all have the right context.
~/Code/storefront
code . ~/Code/storefront
code .
pnpm dev ~/Code/platform
code .
docker compose up The problem
A workspace shortcut only solves half the startup routine
Opening the editor still leaves you navigating to the repository, remembering the dev command, and finding a place for its output. macOS Shortcuts can launch scripts, but it is not a persistent development terminal.
The Shell Click answer
Make the project folder the source of context
Save code . on its own or combine editor launch with the project command in a multiline shortcut. Shell Click starts from the chosen folder and keeps the terminal available for the work that follows.
What stays attached
The command, its context, and its terminal
Repository remembered
Every shortcut starts from its explicit project folder without a preliminary cd.
Multiline startup
Open the editor and run the project setup from one reusable command definition.
Terminal remains available
Keep output and keyboard input attached after the editor has opened.
Why it fits
A launcher that stays useful after launch
Return to the saved command to inspect output, type another command, follow a detected localhost port, or stop the running process.
Shell Click for macOS
From project choice to running code.
Save the folder and startup command once, then launch the project from the menu bar whenever you return.