What Claude Squad does well
It is light, fast and free under AGPL-3.0. You start Claude Code, Codex, OpenCode, Amp, Aider or Gemini in separate sessions from one terminal, let them run in the background, and review each change before applying it. For people who live in the terminal on macOS or Linux, it does the job well.
The Windows problem
Claude Squad requires tmux and the GitHub CLI. tmux is a terminal multiplexer built for Unix systems, so on Windows the usual route is to run everything inside WSL, including your agents and your repository. That works, but it splits your setup in two: Windows for your editor and tools, Linux for the agents.
Coterie: native on Windows
| Claude Squad | Coterie | |
|---|---|---|
| Runs on | Terminal with tmux | Native Windows app |
| Isolation | Git worktree per session | Git worktree per task, and no two tasks on the same files at once |
| Planning | You start each session | An architect model splits the goal into tasks; you confirm |
| Review | You review each diff | A model from another provider reviews, Coterie runs your tests, then you decide |
| Usage limits | Not in the docs | Work moves to an agent that still has room |
| Seeing the work | Terminal list of sessions | A live map of goals, tasks and agents |
Coterie uses the official Claude Code, Codex and Antigravity CLIs on Windows with your own sign-ins, and never reads their credentials.