squadra

Squadra 3+

Your coding agents, one team — and proof for every step.

The most complete team skill for Claude Code, Codex and Cursor.

Free and open source — MIT licence, no account, everything runs on your machine.

Version 3.10.2 · Free · MIT · Local toolkit · Python 3.12+ · macOS / POSIX

English · Italiano · Privacy

What's new · Get started · Example prompts · First steps · Dashboard · Plugins · Decisions · Workflow · Checkpoints · Commands · Community

Static, behavioral and dependency checks, excluding tests/. Passing means no HIGH or CRITICAL findings; lower-severity findings remain in the report. Click the badge for results.

Install it with one sentence. Paste this into Claude Code, Codex or Cursor:

Install Squadra by following https://github.com/dagoSte/squadra/blob/main/SETUP.md: show me the plan first, wait for my yes, then install it and check that it works.

The agent checks what you already have, shows each command with what it changes and how to undo it, waits for your yes, installs and runs a one-second check.

One act stays with you: /reload-plugins in Claude Code, or a new session in Codex or Cursor.

Other ways to install: Installation.

Watch the 80-second tour — turn the sound on in the player:

https://github.com/user-attachments/assets/69f512be-775c-40ae-95c2-e1e403b3f5d1

What's new

3.10.2 — messages that always arrive, and a dashboard that keeps up with a working squad

The coordinator can deliver every message to its window, the dashboard updates only what changed, and the search box finds past work by the words people wrote. The registry format does not change.

Watch the two-minute film of what's new — turn the sound on in the player:

https://github.com/user-attachments/assets/6ea747a5-a993-4aa7-a58d-1b2b7f908720

• Install with one sentence. Paste the sentence at the top of this page into your coding agent: it shows the plan, waits for your yes, installs and checks (SETUP.md).
• Small changes take minutes. Before starting, the agent tells you how many minutes it needs. A small change is simply made, with at most one check. A read by another window or the whole test suite runs only when you or the coordinator ask for it; for an important change it is suggested, with its time.
• The squad starts from Claude. A Codex window called first no longer coordinates windows it cannot see or wake: it tells you which sentence to type in a Claude window, and that window introduces itself to every window, the Codex one included.
• Messages always find their way. The coordinator can deliver any message, including one written by a sandboxed Codex window, and every delivery attempt is recorded. A Claude window receives its own mail as it arrives with squadra inbox --follow. A message to a Codex window that nobody has delivered yet is listed first, as «to forward», with how long it has been waiting.
• Waits that tell the truth. The waits list only what is still open: a closed task's confirmations leave it, and a plan waiting for its reader shows up there.
• Search. The search box finds past work by the words people wrote, in any order and with or without accents, including decisions, questions and reviews. The dropdown shows the newest results first and ends with a ready-made question for your agent.
• Newest first, everywhere. Every list and task picker shows the latest items on top.
• A dashboard that keeps up. After a new event the page updates only what changed; an idle page costs almost nothing, and a search sends only its results.
• Shorter answers. task, brief and start print a short summary. Plain inbox shows the messages waiting for you plus the latest 10; --all shows everything.
• A safer registry. A new registry folder is ignored by Git, so it cannot be committed by accident. A slow write holds the other windows only briefly. doctor is read-only and reports a damaged cache; doctor --repair fixes it and --quick is a fast check. Commands explain errors in plain words. A file leaked into the registry can be removed with a recorded decision.
• Save and restore you can rely on. save works on large projects and on repositories that track .env.example; the way back to an older version works with either version; a save package restores after you open it, and stashed work comes back.
• Usage and Balance measure every window registered as the guide shows (--session), also on machines with many saved conversations.
• Install anywhere. The installer works under a shared-group umask and with a linked home folder. On Python older than 3.12 it refuses with one clear line.
• English stays English. An English workspace gets English in every command.
• Joining and presence. A new window can answer its first presence call, and the coordinator's own sweep keeps the coordinator active.
• Waiting in line. resource acquire --wait SECONDS keeps your place in line for a busy resource, such as the test gate, instead of failing until it is free: windows that wait with --wait get it in the order they asked, and nothing is recorded while they wait. prove checks before it starts that the run covers the task's requirements, so a long proof is never thrown away for a missing --covers.
• One proof for both final reads. prove --also <task> lets one run of the suite serve several tasks on the same frozen code, such as a release's Claude and Codex final reads; each task still checks its own requirements. Use it when every reader's Squadra lists --also in squadra prove --help; otherwise prove each task on its own.
• Windows that are gone stop filling the waits. Mail to a window you put in stand-by shows as one line per window, for example «12 messages to core-A on stand-by (window closed)», and comes back as soon as the window returns.
• A registry that stays small. The registry's journal file goes back to a small size after write