BRIX vs Claude Squad: which one should you use to run parallel agents?

What is Claude Squad?

Claude Squad (github.com/smtg-ai/claude-squad) is a terminal app that manages several AI agents in separate workspaces from one terminal window. It is open source under AGPL-3.0 and installs with Homebrew or a shell script.

brew install claude-squad
cs                                   # open the session list
cs -p "codex"                        # run another agent instead of Claude Code
cs -y                                # experimental: auto-accept prompts

• Agents: Claude Code by default; Codex, Gemini, Aider and other local agents through the -p flag.
• Isolation: each session runs in its own tmux session on its own git worktree and branch.
• Workflow: keyboard-driven list of sessions, diff preview, pause and resume, commit and push to GitHub with one key.
• Prerequisites: tmux and the GitHub CLI gh.
• Price: free.

Facts taken from the Claude Squad README and releases page on 2026-10-03. The project moves fast; check the repository before deciding.

What is BRIX?

BRIX is a desktop app for Claude Code orchestration on macOS (Apple Silicon) and Windows. You run Claude Code, Codex, Antigravity and OpenCode in a grid or on a free canvas, on the subscriptions you already pay for. Agents can be connected to each other, organized into squads with a lead agent, and given persistent memory. On the PRO plan, the same product base feeds studios for copy, ads, carousels and video.

Where Claude Squad gives you a clean list of independent sessions, BRIX gives you a team: agents that send each other prompts, read each other and deliver together. See how BRIX works.

How do BRIX and Claude Squad compare?

Where is Claude Squad better than BRIX?

• It is free and open source. You can read the code, fork it and run it anywhere tmux runs. BRIX is a paid, closed-source app.
• It lives in your terminal. If you already work in tmux over SSH, Claude Squad fits that habit with no window to switch to.
• Worktree isolation by default. Every session gets its own branch, so parallel agents cannot edit the same files. In BRIX, agents in one workspace share the folder; you split the work by role or create worktrees yourself.
• Any agent with a command. cs -p "aider ..." runs whatever CLI you point it at, including local models through Aider.
• Light. A single binary and two dependencies.

Where is BRIX better than Claude Squad?

• Agents that collaborate. Draw an edge between two terminals and they can prompt and read each other. Name a lead and it recruits workers, splits the task and follows up. More in orchestrate a team of AI agents.
• A visual workspace. Grid or canvas, with notes, task lists and images that agents publish next to their terminal. The Scene view shows who is working and who is waiting for you without opening each session.
• Persistent memory. SuperAgents keep what you taught them across sessions. See AI agents with persistent memory.
• From code to sales. The product base in Markdown (product.md, publico.md, oferta.md) feeds the sales page, ad creatives, carousels and video on the PRO plan. Claude Squad stops at the commit.
• Operable from outside. The BRIX MCP and the medmaestri CLI let Claude Desktop, Codex or a script create squads, send prompts and read answers.

When should you choose Claude Squad, and when BRIX?

Choose Claude Squad if

• You live in the terminal and want a keyboard-only tool.
• You want open-source software you can audit and modify, at no cost.
• Your agents work on independent tasks and each one should stay on its own branch.
• You want to run agents like Aider or Gemini next to Claude Code.

Choose BRIX if

• You want agents that coordinate, with a lead that splits and checks the work.
• You prefer a desktop app with a canvas over a TUI.
• You build a product and also write its copy, ads and video, and want one base feeding both.
• You want agents that remember your rules and corrections between sessions.

How do you move from Claude Squad to BRIX?

1. 1

   Install BRIX

   Download it from the download page for macOS (Apple Silicon) or Windows.

2. 2

   Keep your agent logins

   BRIX uses the Claude Code, Codex, Antigravity or OpenCode already on your machine, with the same login.

3. 3

   Recreate your sessions as a team

   Instead of N independent sessions, create a supervisor plus workers in one command, or pick a ready-made squad.

4. 4

   Keep branch isolation if you need it

   Create git worktrees yourself and open a BRIX terminal in each folder.

medmaestri team --supervisor claude --workers codex --count 3

STARTER is free for 7 days with no card, and there is a 7-day guarantee after you subscribe. See the plans.

Frequently asked questions

Keep reading

• BRIX vs Conductor: which one should run your Claude Code agents?BRIX vs Conductor, checked October 2026: worktrees, platforms, pricing and agents. Where Conductor wins, where BRIX wins, and how to pick the right one.
• How to orchestrate a team of Claude Code agentsOrchestrate Claude Code and Codex agents as a team: a lead agent, canvas edges as permissions, ready-made squads, a task list and a CLI to spawn, ask and check.
• How to run multiple Claude Code agents in parallelHow to run multiple Claude Code agents in parallel: terminal tabs, tmux, git worktrees, Conductor, Claude Squad, and connected agents with a lead in BRIX.