Claude Squad

Claude Squad is a single Go binary (cs) with a terminal UI. It does not talk to models itself: each new instance starts the configured agent program (claude by default) inside a detached tmux session whose working directory is a fresh git worktree on its own branch. The TUI reads the tmux panes to show a preview and computes a diff of the worktree.

There is no coordination between agents. The person using the TUI is the orchestrator, creating sessions (optionally with a starting prompt), attaching to them to reprompt, and deciding when to commit, pause, resume or push. With --autoyes, a daemon process polls all sessions and answers their prompts so they can keep running unattended.

State is kept on disk under the config directory (~/.claude-squad/): the config file with the default program and profiles, plus JSON files listing instances so sessions can be restored after a restart; cs reset clears them. Work itself lives in the git worktrees and branches.

By default every agent runs with its own permission prompts, and the user answers them by attaching to the session (enter) and detaching again (ctrl-q). Changes are reviewed in the diff tab before anything leaves the machine: c commits and pauses a session, and only s pushes the branch. The experimental --autoyes flag removes this step by accepting prompts automatically for Claude Code and Aider, including from a background daemon. Independently of that flag, the code presses Enter when a Claude Code session shows its folder-trust or "new MCP server" prompt, so those defaults are accepted without the user seeing them.

brew install claude-squad

# Prerequisites: tmux, gh, and an agent CLI (claude is the default program)
brew install claude-squad
ln -s "$(brew --prefix)/bin/claude-squad" "$(brew --prefix)/bin/cs"

cd ~/code/my-repo            # run inside a git repository
cs                           # n = new session, N = new session with a prompt
cs -p "codex"                # use Codex instead of Claude Code
cs -p "aider --model ollama_chat/gemma3:1b"
cs -y                        # experimental: auto-accept prompts (Claude Code, Aider)

# In the TUI: tab = preview/diff, enter = attach, ctrl-q = detach,
# c = commit and pause, r = resume, s = commit and push the branch
cs debug                     # prints config paths (~/.claude-squad/config.json)

• Requires tmux and the GitHub CLI (gh); sessions are git worktrees, so run it inside a git repository.
• Homebrew installs the binary as claude-squad; the README adds a cs symlink. The install script puts cs in ~/.local/bin.
• If you see failed to start new session: timed out waiting for tmux session, update the agent program (for example claude) to its latest version.
• For Codex the README says to export OPENAI_API_KEY first.
• --autoyes is experimental and only handles Claude Code and Aider prompts; its daemon keeps accepting prompts after the TUI exits.
• Open issues: the Windows binary fails on new sessions (#275), prompts can be sent to Codex before it is ready (#266), and sessions may miss custom environment variables when an existing tmux server is reused (#277).

No MCP server or client is documented. The only MCP reference in the code dismisses Claude Code's 'new MCP server' prompt automatically.

Claude Code is the default. The README documents Codex (cs -p "codex"), Gemini CLI and Aider, and any other CLI can be started with -p or a profile. The GitHub description also names OpenCode and Amp, but the README gives no setup for them.

Yes. It is AGPL-3.0 licensed and no paid product is documented. Contributors must sign a CLA.

Each session runs in its own tmux session and its own git worktree on a separate branch.

It is an experimental flag that accepts prompts automatically for Claude Code and Aider. A background daemon keeps applying it to all sessions after the TUI exits.