<div align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset="assets/squadra-logo-dark.svg"> <img src="assets/squadra-logo-light.svg" alt="Squadra" height="96"> </picture>

Squadra 3+

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

Coordinate Claude Code, Codex and Cursor with shared tasks, independent reviews and a local dashboard.

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

Version 3.10.4 · Python 3.12+ · macOS / POSIX

English · Italiano · Privacy

Overview · Install · First steps · Prompts · Dashboard · Plugins · Commands · Guides · What's new · Community

</div>

What the security scan covers.

<a id="overview"></a>

What Squadra does

Squadra helps several windows of coding agents work on one project as a team: one coordinates, others build, and a window that did not write the code reviews it. Assignments, decisions, executed checks and review reports stay in one shared registry on your computer.

Use it when work spans several agent sessions and you need to see who owns each task, which code was checked and what still needs a decision. Each window can work in its own checkout while sharing the same record.

| Part | What it does | |---|---| | Skill | Gives the agents the coordination workflow to follow. | | CLI | Records tasks, messages, checks and decisions. | | Dashboard | Shows progress, evidence and requests for your input. |

Team setup: start with a Claude coordinator, then join your Codex, Claude or interactive Cursor windows. The team rules explain the roles and limits.

The Summary on a synthetic Atlas registry (Italian, dark theme). Recorded texts such as briefs, the owner's words and messages stay as written, here in Italian. The examples contain no customer data and do not measure model quality.

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

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

<a id="what-makes-it-different"></a>

Why use Squadra

• One registry for every window. Assignments, proofs and decisions stay on your computer, not in a chat's memory.
• Whoever writes it does not review it. Every change is checked by a window that did not write it.
• Proof bound to the exact code. If the code changes after the proof, proof and review no longer count.
• Confirmed before work starts. A task starts only when its recipient confirms receiving it.
• Questions with the sentence ready. When a decision is yours, you get the options, a recommendation and the exact words to answer.
• A dashboard in plain words, in Italian or English, to follow everything live.
• Claude, Codex and Cursor together, and open to community plugins.
• One view of what every AI window spends. Tokens per window, model and task across Claude Code and Codex, with advice on which window or model should take the next task, computed on your computer.

<a id="start"></a>

Installation

Requirements: Python 3.12+, Git and a browser for the dashboard. The runtime uses the Python standard library; Node.js is required for selftest. macOS / POSIX is the tested environment. Full requirements and platform limits.

Recommended: install with one sentence

<a id="one-sentence"></a> 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.

<details> <summary><strong>Other installation methods: plugin or standalone command</strong></summary>

With /plugin

In Claude Code:

/plugin marketplace add dagoSte/squadra
/plugin install squadra@squadra

In a terminal, for Codex:

codex plugin marketplace add dagoSte/squadra
codex plugin add squadra@squadra

The plugin brings the skill, its scripts, references and dashboard. It does not put the squadra shell command on your PATH: agents run python3 <skill folder>/scripts/squadra.py, also for the instructions Squadra prints, such as squadra ack …. To have the squadra command itself, use the standalone installer below instead of the plugin. Use either the plugin or the standalone installer, not both, so the skill is not registered twice.

Standalone installer (adds the squadra command)

git clone https://github.com/dagoSte/squadra.git
cd squadra
python3 -B scripts/install.py \
  --backup "$HOME/.local/state/squadra/install-backup-001"
export PATH="$HOME/.local/bin:$PATH"
squadra --version

Install from a clean, committed checkout with a new backup directory each time; the installer keeps your previous skills and launcher, so you can roll back. The export PATH line lasts for that terminal only: add it to your shell profile (for example ~/.zshrc or ~/.bashrc) so new terminals find squadra. Without installing, run python3 -B scripts/squadra.py <command>. Details and rollback.

</details>

<a id="updating"></a>

<details> <summary><strong>Updating an existing installation</strong></summary>

Updating

With /plugin. In Claude Code, run /plugin marketplace update squadra, then /plugin update squadra@squadra, then restart Claude Code. For Codex, run codex plugin marketplace upgrade, then codex plugin add squadra@squadra again.

With the standalone installer. From 3.6.1 on, releases keep their history: run git pull, then the installer again, with a new backup folder each time. A checkout of 3.6.0 or earlier needs git fetch origin and git reset --hard origin/main instead, which discards any local edit in that checkout.

git pull
python3 -B scripts/install.py \
  --backup "$HOME/.local/state/squadra/install-backup-002"
squadra --version

Every release raises the version number, except a refresh that adds to a release under the same number, as 3.10.2 did on 17 October 2026. Plugins installed from the Store keep their version until squadra plugin install <name> runs again from the new release (Plugins bundled in your release). Open windows keep the version they read until they restart, and a running squad keeps its protocol until you switch it explicitly.

Updating from 3.10.3 or 3.10.2 to 3.10.4: the registry stays as it is.

• Windows can move one at a time. 3.10.2, 3.10.3 and 3.10.4 windows share the same registry; nothing is converted.
• Update the coordinator first. The rule that the other model reads binds the tasks a 3.10.4 window records, and an older window does not check it at check or close. Tasks recorded before the update keep closing as before.
• Plugins from the Store: run squadra plugin install <name> again, as after every release.

Updating from 3.10.1 to 3.10.2: the registry stays as it is.

• Windows can move one at a time. 3.10.1 and 3.10.2 windows share the same registry while you update them; nothing is converted.
• Two things wait for the last window. A settings change made from a 3.10.1 window puts the two new wait thresholds (to-forward and plan) back to their defaults. And removing a leaked file with a recorded decision makes a 3.10.1 window's full audit and dashboard fail on the missing file, so update every window before you remove one.
• Plugins from the Store: run squadra plugin install <name> again, as after every release.

Updating from 3.10.0 or earlier to 3.10.1: less repeated history work, and every window must move together.

• Before you update, the coordinator saves the squad: squadra save --actor <coordinator> --to <a new folder>. It is your way back.
• Your registry is read as it is. Nothing is converted and the history already written is not touched. From the first command on 3.10.1, new events are written in the lighter format.
• Update every window at once, Claude Code and Codex. A window still on 3.10.0 stops at the first new event with Event integrity failure at sequence N. That is on purpose: an old version stops rather than accept events it cannot read. Nothing is lost: update that window and it carries on.
• No way back on the same registry. After the update, 3.10.0 cannot use that registry. To go back, restore the save you made before updating, with either version, then keep using the old version on the restored copy: the first command of 3.10.1 or later on it writes the newer format again.
• If in doubt, run squadra doctor on 3.10.1: it says when a registry needs 3.10.1 or later.
• Plugins from the Store: run squadra plugin install <name> again, as after every release.
• If you installed Squadra from the Claude directory, you get the version the directory lists until it moves to 3.10.1.

The first window to write an older or moved registry builds its cache; other windows wait. If a command says registry busy, retry, retry after that first write finishes.

</details>

<a id="requirements"></a>

<details> <summary><strong>Full requirements: self-test, native runners and platform limits</strong></summary>

Requirements: Python 3.12+, Git and the Python standard library. Node.js runs the dashboard's JavaScript checks in the test suite and in selftest: without it they fail, they are never skipped. A browser for the dashboard; the Codex or Claude CLI only for the native runners. macOS/POSIX is the tested process environment; Windows process controls and recovery with submodules, LFS or sparse checkouts are not qualified.

</details>

<a id="first-steps"></a>

First steps

After installation, give instructions in plain words; the agents run the commands. A **windo