Windows walk-through

Claude Squad on Windows: what works, what breaks, what else to try

Updated November 17, 20268 min read

Claude Squad is a free terminal app that runs several coding agents (Claude Code, Codex, Gemini, Aider and more) side by side, each on its own git branch. It is built on tmux, a Mac and Linux tool, so on Windows the reliable way to run it is inside WSL. This page follows a Windows user from first try to working setup, including the open bug that stops the native Windows build, and the alternatives if the setup feels like too much.

The idea behind Claude Squad

Say you want three things done on your app: a new settings page, a bug fix, and some tests. With one Claude Code window you do them one after another. Claude Squad lets you start all three at once. Each one gets its own session, its own git branch and its own copy of the code, so they can't overwrite each other.

You see a list of sessions on the left and a preview of the selected one on the right. A second tab shows the diff (the exact lines that changed). When a task looks good, one key commits it and pushes the branch to GitHub. It is made by smtg-ai, is open source under the AGPL-3.0 licence, and costs nothing. You still need your own plan for each agent it runs, such as Claude Pro for Claude Code.

By default it starts Claude Code. To run a different agent, you pass its command with -p, for example cs -p "codex" or cs -p "aider".

Why Claude Squad needs tmux, in plain words

Claude Squad's README lists two things you must install first: tmux and gh. Here is what those, and the other words you will meet on Windows, actually mean.

Terminal
The text window where you type commands. On Windows that is usually PowerShell or Windows Terminal.
tmux
A program that runs many terminal sessions inside one window and keeps them alive in the background. Claude Squad uses it to run each agent.
gh
GitHub's command line tool. Claude Squad uses it to push branches to GitHub.
WSL
Windows Subsystem for Linux. A real Linux system running inside Windows, made by Microsoft.
Ubuntu
The Linux version WSL installs by default.
Git worktree
A second copy of your project folder that git keeps linked to the same history. Each Claude Squad session gets one.
PTY
A pretend terminal that a program creates so another program thinks it is talking to a real one. This is where the Windows bug lives.

tmux has no native Windows version. That one fact explains most of the trouble Windows users have with Claude Squad. Our Claude Code with tmux page covers tmux on its own if you want to learn it.

First attempt: the native Windows build and issue #275

Claude Squad's releases do include a Windows file, so the natural first move is to download it. It opens. Then you press n to make a new session, and it fails straight away.

Watch out

GitHub issue #275 on the Claude Squad project, opened on April 7, 2026, reports this exact problem with the v1.0.17 Windows binary: "failed to start new session: error starting tmux session: unsupported". The reporter traced it to a library (creack/pty) that has no Windows support. As of November 2026 the issue is still open with no linked fix.

So the native route is a dead end for now. Don't spend time reinstalling or changing settings; the problem is in the code, not on your PC. The working route is WSL.

Second attempt: installing Claude Squad through WSL

WSL needs Windows 10 version 2004 or later (build 19041 or higher), or Windows 11. Give yourself a quiet hour for the first setup, because you will set things up twice: once on the Windows side, once inside Linux.

  1. 1

    Install WSL

    Right-click PowerShell, choose Run as administrator, and run wsl --install. This turns on WSL and installs Ubuntu. Restart your PC when it finishes.

  2. 2

    Create your Linux user

    Search for Ubuntu in the Start menu and open it. On this first run it spends a minute unpacking, then asks you to pick a Linux username and password. Remember the password; you need it for sudo (admin) commands.

  3. 3

    Install tmux and git

    Inside Ubuntu, run the apt commands shown below. apt is Ubuntu's app installer.

  4. 4

    Install the GitHub CLI

    Follow the Debian and Ubuntu steps on cli.github.com, then run gh auth login and sign in to GitHub.

  5. 5

    Install Claude Code inside Linux

    Your Windows copy of Claude Code doesn't count here. Run Anthropic's Linux install command inside Ubuntu, then run claude once to sign in.

  6. 6

    Install Claude Squad

    Run the install script from the Claude Squad README. It puts a program called cs in ~/.local/bin.

  7. 7

    Put your project inside Linux

    Clone or copy your project into your Linux home folder (for example ~/code/myapp), not under /mnt/c. Files on the Windows drive are much slower from inside WSL.

  8. 8

    Start it

    Move into the project folder with cd and run cs. Press n for a new session and type your first task.

# In PowerShell (as administrator)
wsl --install
# Inside Ubuntu
sudo apt update
sudo apt install tmux git
curl -fsSL https://claude.ai/install.sh | bash
curl -fsSL https://raw.githubusercontent.com/smtg-ai/claude-squad/main/install.sh | bash

If cs is "not found" after installing, close Ubuntu and open it again so it picks up the new ~/.local/bin folder. If wsl --install only prints help text, WSL is already partly installed: run wsl --list --online to see the Linux versions on offer and wsl --install -d Ubuntu to add one.

Claude Squad install on Mac and Linux, for comparison

On a Mac with Homebrew, the whole install is two lines. The second one makes the short cs command work:

brew install claude-squad
ln -s "$(brew --prefix)/bin/claude-squad" "$(brew --prefix)/bin/cs"

On Linux, the same install script used in the WSL steps above works. Either way you still need tmux and gh first. This gap, two lines on a Mac against eight steps on Windows, is the main reason Windows users go looking for a Claude Squad alternative.

Living with Claude Squad: keys and habits

Once it runs, Claude Squad is driven from the keyboard. These are the keys from its README that you will use every day:

KeyWhat it does
nStart a new session
NStart a new session with a prompt
Enter or oOpen the selected session so you can type to the agent
Ctrl+qLeave the session and go back to the list
TabSwitch between the preview and the diff
sCommit and push the branch to GitHub
cCommit changes and pause the session
rResume a paused session
DDelete the selected session
?Show help

There is also an experimental -y (auto-yes) flag that makes sessions accept prompts on their own. It can save clicks, but it also lets agents run commands without asking you. Leave it off until you trust your setup.

One habit to build: check back often. Claude Squad previews one session at a time, and its README doesn't mention sounds or pop-ups when an agent is waiting. A session can sit idle for a long time if you don't look.

WSL tips that save time

  • See your Linux files in Windows. Inside Ubuntu, run explorer.exe . to open the current folder in File Explorer.
  • Open Ubuntu fast. Add it as a tab in Windows Terminal, so your agents are one click away.
  • When things get stuck, run wsl --shutdown in PowerShell and open Ubuntu again. It restarts Linux, which clears most odd states. Any running sessions will stop, so commit first.
  • Sign in once per side. Claude Code, Codex and gh inside Linux each need their own sign-in, separate from Windows.
  • Previews still open in your Windows browser. If an agent starts your app's dev server inside WSL, you can usually open it from Windows at the localhost address it prints.
  • Keep one place for your code. Editing the same project from both Windows and Linux copies leads to confusion. Pick the Linux copy and stick to it.

When WSL feels like too much: other ways to run agents in parallel

If the steps above put you off, you have three simpler routes on Windows.

The Claude desktop app

Anthropic's own app runs on Windows (x64 and ARM64). In its Code tab, press Ctrl+N for another session and turn on Worktree before you start so each session gets its own copy. Session copies need git, so install Git for Windows. It only runs Claude Code.

Several terminals and git worktrees

You can copy what Claude Squad does by hand: make a worktree per task and open a Windows Terminal tab in each. Our Claude Code worktrees guide shows the commands. It is free but you do all the tracking yourself.

VibeCodingDeck

VibeCodingDeck is a desktop app for Windows 10/11 and Apple-silicon Macs with no tmux and no WSL. Instead of a list, you see up to 12 agents at once in a grid, from Claude Code, Codex, Gemini, Copilot, Antigravity, Grok, Qwen or Kimi. Each can work on its own safe copy (a worktree under the hood). A status light and alert sounds tell you which one is waiting, a usage meter shows how much of each plan is left, and your layout and conversations come back after you close the app. Unlike Claude Squad it is paid: $29 a month or $249 a year. See the Claude Code dashboard page for what the grid looks like, or Claude Code on Windows for the native install.

Claude Squad (WSL)Claude desktop appVibeCodingDeck
Setup on WindowsWSL, tmux, gh, Linux copy of each agentInstaller plus Git for WindowsInstaller
AgentsClaude Code, Codex, Gemini, Aider and othersClaude Code only8 agent types
How you watch themOne at a time from a listSidebar of sessionsUp to 12 panes at once
Told when one is waitingNot in its READMENotification when a task finishesStatus light and alert sounds
Price (Nov 2026)FreeIncluded with Claude plans$29 a month or $249 a year

If you are on a Mac or Linux and like the terminal, Claude Squad is a good free choice. On Windows, the right pick mostly depends on one thing: are you happy to keep a Linux system running next to your normal one? If yes, Claude Squad works well in WSL. If not, pick one of the desktop apps above.

Sources

Run up to 12 AI coding agents in one window.

Claude Code, Codex, Gemini, Grok and more, side by side. Windows and Mac. From $29 a month.

Get started

Keep reading