Third-Party Terminal Integration
Last updated: 2026-09-02
Overview
By default, Dev WorkDir runs your scripts in the system Terminal.app. Pro lets you choose your favorite terminal instead, so “double-click to run” opens exactly where you like to work.
- Free: scripts open in system Terminal.app.
- Pro: pick from 6 supported third-party terminals.
Supported Terminals
| Terminal | Injection method |
|---|---|
| Terminal.app | AppleScript (default) |
| iTerm2 | AppleScript |
| Warp | Launch Config YAML |
| Ghostty | exec |
| Alacritty | exec |
| Kitty | exec |
| WezTerm | exec (wezterm start --) |
How to Choose
- Open Settings → Default Terminal.
- Select your installed, supported terminal (rows show a lock icon for non-Pro users).
- Pro users get the selected terminal for script runs and “Open in Terminal”.
- Free users see the list but can’t select — system Terminal is used and a hint explains why.
Under the Hood
- Terminal detection checks the app is installed (by bundle ID) before offering it.
- Execution goes through a small helper script (
run_terminal.sh) that injects your project env vars and keeps an interactive shell alive. - If your chosen terminal is missing or unsupported, WorkDir falls back to system Terminal.
Related: Pro Pricing.