At a glance
A multi-model terminal harness with interactive and headless modes, parallel subagents, MCP, policy-based permissions, worktrees, session checkpoints, hooks, skills, and IDE context integration.
Good choice if
- Terminal users who need explicit allow, ask, and deny policy rules
- Parallel exploration and implementation with constrained subagents
- Headless CI runs that must fail closed instead of waiting for approval
Check before choosing
- Project path controls and Git worktrees constrain file organization but do not provide an OS security boundary for shell execution
- Headless editing requires `--yolo`, which enables writes and shell commands together rather than granting a narrow mutation capability
- Checkpoints are per-session, omit files over 10 MB, and cannot reverse shell or external-service side effects
See 2 more considerations
- Goal completion is judged inside the product workflow rather than independently replicated evidence; unattended goals still need explicit budget and stop policies
- Monitors, cron schedules, background commands, and background subagents inherit the host execution boundary unless the user supplies an external sandbox