Double-Click to Run
Last updated: 2026-08-05
Overview
Double-click any project card to run it. Dev WorkDir automatically detects the right command and opens it in Terminal.
No more typing npm run dev or python main.py — just double-click and go.
How It Works
Auto-Detection
Dev WorkDir scans your project and detects common run scripts:
| Project Type | Detected Commands |
|---|---|
| JS/TS (npm) | npm run dev, npm start, npm run build |
| JS/TS (pnpm) | pnpm dev, pnpm start |
| JS/TS (yarn) | yarn dev, yarn start |
| JS/TS (bun) | bun dev, bun start |
| Python | python main.py, python app.py |
| Rust | cargo run, cargo watch -x run |
| Go | go run main.go, go run . |
| Ruby on Rails | rails server |
| Ruby (Sinatra) | ruby app.rb |
| Docker | docker compose up |
| Makefile | make run, make dev |
Execution
When you double-click:
- Dev WorkDir opens Terminal.app
- It
cds into the project directory - It runs the detected (or custom) command
- You see the output in Terminal as usual
Customizing the Double-Click Action
Every project can have its own double-click action.
Set a Custom Command
- Select the project
- In the detail view, find “Double-Click Action”
- Choose from the auto-detected scripts, or
- Enter your own custom command
Examples of Custom Commands
# Run with a specific script
npm run dev:debug
# Run tests
npm test
# Start Docker
docker compose up --build
# Custom Python script
python scripts/start.py
# Open in editor only
# (set to "Open in Editor" instead of a script)
Environment Variables
If you’ve set environment variables for the project, they’re automatically injected when you double-click to run.
This means you don’t have to manually export variables or create .env files for every project.
Tips
1. Different Actions for Different Moods
You can have multiple scripts configured:
- Double-click:
npm run dev(default) - Right-click → Run: choose from other scripts like
npm run build,npm test
2. Quick Editor Access
Don’t want to run? Just single-click to select, then press Enter or use the “Open in Editor” button.
3. Terminal Integration
The command runs in your normal Terminal.app, so:
- All your shell aliases and configs work
- You can interact with the process normally
- Ctrl+C to stop works as expected
4. First Run Setup
The first time you run a project, you may need to:
- Install dependencies first (e.g.,
npm install) - Set up environment variables
- Configure your custom run command
Troubleshooting
Nothing happens when I double-click
- Check if Terminal.app is available
- Make sure a double-click action is configured for that project
- Try right-clicking and manually selecting a run option
The command fails
- Check the Terminal output for errors
- Make sure dependencies are installed
- Verify the command is correct in the project settings
It opens the wrong project
- Make sure you double-clicked the right card
- Check if multiple terminal windows are open
Double-click. Run. Code. That’s vibe coding.