Spawn independent Claude Code sessions in new terminal windows (Ghostty, iTerm2, Terminal.app). Use when the user asks to open new sessions, launch parallel workers, or run Claude in a separate terminal. Supports interactive and non-interactive modes with multi-session parallel spawning.
Runs independent Claude Code sessions in new terminal windows. Supports Ghostty (default), iTerm2, and macOS Terminal.app.
Collect the following two pieces of information interactively:
backend-refactor, test-writer, docs-update)How to collect:
ls or findRun the scripts/spawn.sh script from this skill:
bash <this skill's path>/scripts/spawn.sh --name "<session-name>" --dir "<project-directory>" [options...]
| Option | Description | Default |
|---|---|---|
--name, -n | Session name (required) | — |
--dir, -d | Project directory (required) | — |
--terminal, -t | Terminal to use (ghostty, iterm, terminal) | ghostty |
--prompt, -p | Initial prompt (non-interactive mode) | None (interactive) |
--resume, -r | Resume existing session | false |
--model, -m | Specify model | Default model |
--print | Non-interactive + stdout only | false |
--dangerously-skip-permissions | Skip all permission prompts | false |
Single session spawn:
User: "Open a new session"
→ Ask for session name and directory, then spawn
Information already provided:
User: "Launch Claude as backend-worker in ~/projects/my-app"
→ Spawn immediately
Parallel multi-spawn:
User: "Spawn 3 sessions in parallel - API, DB, Test"
→ Call spawn.sh 3 times (each with & for background)
With a prompt:
User: "Tell it to write tests in ~/projects/game"
→ Pass instructions via --prompt option
/rename main for easy identification among spawned sessions/config → Enable Remote Control for all sessions → true) so all sessions can be monitored from phone or browser via claude.ai/code--prompt, the terminal window closes automatically after task completion--resume, it continues an existing session with the same name--terminal to select the terminal (default: ghostty)