Squadrant

Squadrant

Run your coding agents like an engineering team. You're the manager — Squadrant gives you **captains** who plan and delegate, and **crews** who write the code.

The mental model

You
 │
 ├── squadrant launch    →  Captain (project A)
 │                                     │
 │                                     └── squadrant crew spawn  →  Crew, Crew, …
 │
 └── squadrant launch  →  Captain (project B)
                                        └── …

• You — set direction, make the calls only you can make.
• Captain — one per project, lives in cmux, plans and delegates. Your standing project lead.
• Crew — a fresh interactive sub-session the captain spawns to actually write the code, then reports back and signals when it's done or blocked.

One person, operating like an engineering org.

Squadrant is also moving to support every major coding agent — Claude Code, Codex, Cursor, Gemini CLI — not just Claude Code. Claude Code is the reference implementation today; other agents land through the plugin system's driver abstractions and the upcoming cross-agent projection layer ([#31](https://github.com/tu11aa/squadrant/issues/31)). See [`docs/specs/2026-04-24-multi-agent-direction.md`](docs/specs/2026-04-24-multi-agent-direction.md).

Why you'd want it

• Run several projects at once — one captain per project, each with its own context, all supervised from the same session.
• Delegate instead of micromanage — hand a task to a crew and let it work; you don't watch every keystroke.
• Agents signal you, not the other way around — crews report CREW DONE / CREW BLOCKED / CREW NEEDS INPUT instead of you polling a pane to see if it's finished.
• Drive it from your phone — optional two-way Telegram bridge, so you can delegate and get notified without being at your desk.

What it feels like

squadrant launch brove
  → Captain boots in cmux

You (in the captain pane