SkillsApr 7, 2026·2 min read

Claude Squad — Manage Multiple AI Agent Sessions

Terminal multiplexer for AI coding agents. Run multiple Claude Code or Aider sessions in parallel with tmux-based management, status tracking, and git worktrees.

TL;DR
Claude Squad lets you run multiple Claude Code or Aider sessions simultaneously with tmux-based management and status tracking.
§01

What it is

Claude Squad is a terminal multiplexer purpose-built for AI coding agents. It lets you run multiple Claude Code, Aider, or other AI coding sessions in parallel, each in its own tmux pane with independent git worktrees. A status dashboard shows which sessions are active, waiting for input, or completed.

Claude Squad is designed for developers who want to parallelize AI-assisted development across multiple tasks or branches simultaneously.

§02

How it saves time or tokens

Running one AI coding session at a time creates a bottleneck. While Claude Code works on a refactoring task, you wait. Claude Squad eliminates that bottleneck by letting you launch multiple sessions: one for refactoring, one for tests, one for documentation. Each session runs independently with its own git worktree, so there are no merge conflicts during parallel work. The status dashboard tells you which sessions need your attention, so you can context-switch efficiently.

§03

How to use

  1. Install Claude Squad:
go install github.com/smtg-ai/claude-squad@latest

Or download a binary from GitHub releases.

  1. Launch Claude Squad:
claude-squad
  1. Press n to start a new agent session. Each session gets its own tmux pane and git worktree. Navigate between sessions with arrow keys and monitor their status in the dashboard.
§04

Example

A typical multi-session workflow:

# Launch Claude Squad
claude-squad

# Press 'n' — Session 1: "Refactor auth module"
# Press 'n' — Session 2: "Write unit tests for API"
# Press 'n' — Session 3: "Update README with new endpoints"

# Dashboard shows:
# [1] auth-refactor    WORKING   branch: ws/auth-refactor
# [2] api-tests        WAITING   branch: ws/api-tests
# [3] readme-update    DONE      branch: ws/readme-update

# Select session 2, provide input, then let it continue
# When all sessions finish, merge worktrees back
§05

Related on TokRepo

§06

Common pitfalls

  • Not having tmux installed. Claude Squad requires tmux as a dependency. Install it with brew install tmux (macOS) or apt install tmux (Linux) before running Claude Squad.
  • Running too many sessions simultaneously on a machine with limited resources. Each AI session consumes memory and API tokens. Start with 2-3 sessions and scale up based on your hardware and API rate limits.
  • Forgetting to merge worktrees after sessions complete. Claude Squad creates separate git worktrees for isolation, but you must manually merge the results back into your main branch when done.

Frequently Asked Questions

Which AI coding agents does Claude Squad support?+

Claude Squad supports Claude Code and Aider out of the box. Since it uses tmux to manage sessions, it can technically run any terminal-based AI coding agent. You configure the agent command when creating a new session.

How does Claude Squad handle git conflicts between sessions?+

Each session runs in its own git worktree, which is an independent working directory with its own branch. This prevents conflicts during parallel work. You merge the branches after sessions complete using standard git merge or rebase.

Can I use Claude Squad on macOS?+

Yes. Claude Squad works on macOS and Linux. It requires Go for installation (or use a pre-built binary) and tmux for session management. Install tmux with brew install tmux on macOS.

How many sessions can I run simultaneously?+

There is no hard limit in Claude Squad itself. The practical limit depends on your machine's resources and your API rate limits. Each session runs an independent AI agent process, so memory and API costs scale linearly.

Does Claude Squad persist sessions across terminal restarts?+

Claude Squad uses tmux for session management, so sessions persist as long as the tmux server is running. If you close your terminal, you can reattach to the tmux session. However, if the tmux server itself is killed, sessions are lost.

Citations (3)
🙏

Source & Thanks

Created by smtg-ai. Licensed under MIT.

smtg-ai/claude-squad — 5k+ stars

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets