Claude is the default agent, so these commands are equivalent:
start-issue 123
start-issue 123 --agent claudeBy default, Claude receives the repository-native task-router command:
/task-router:route-task {ISSUE_URL}
Use --command to keep the Claude slash-command style but change the command prefix:
start-issue 123 --agent claude --command "/debug"Select a specific Claude model for the session:
start-issue 123 --agent claude --model sonnetUse project config when Claude should be the default for this repository:
mkdir -p .start-issue
echo claude > .start-issue/agent
start-issue 123Launch Codex for a single issue:
start-issue 123 --agent codexLaunch Codex with an explicit model:
start-issue 123 --agent codex --model gpt-5.2The script creates the worktree, renders the portable prompt, and launches:
codex --cd "$WORKTREE_PATH" --dangerously-bypass-approvals-and-sandbox "$PROMPT"Use Codex as your project default:
mkdir -p .start-issue
echo codex > .start-issue/agent
start-issue 123Use a custom prompt file with Codex:
start-issue 123 --agent codex --prompt-file .start-issue/prompt.mdLaunch Kimi for a single issue:
start-issue 123 --agent kimiThe script creates the worktree, renders the portable prompt, and launches:
cd "$WORKTREE_PATH" && kimi -p "$PROMPT"Use an explicit Kimi model:
start-issue 123 --agent kimi --model kimi-k2Use Kimi from the environment without changing project files:
START_ISSUE_AGENT=kimi start-issue 123Use an inline prompt for one run:
start-issue 123 --agent kimi --prompt "Implement {ISSUE_URL} in {WORKTREE_PATH}. Keep changes scoped and run tests."Launch Pi for a single issue:
start-issue 123 --agent piThe script changes into the worktree and launches:
cd "$WORKTREE_PATH"
pi "$PROMPT"Use an explicit Pi model:
start-issue 123 --agent pi --model sonnetUse Pi as your user default for all repositories:
mkdir -p ~/.config/start-issue
echo pi > ~/.config/start-issue/agent
start-issue 123Preview exactly what would happen before launching Pi:
start-issue 123 --agent pi --dry-run