Yes. squad runs. Argusic installed and launched it on a clean machine in 26 minutes, hitting 6 errors on the way, and recorded the session.

How did Argusic test squad?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit fcb7747c7a01. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test squad?

The run that produced this verdict cost $0.15: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does squad take to install?

26 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.

Does squad need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing squad?

6 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for squad?

The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

squad

Squad: AI agent teams for any project

Runssource: GitHub homepageTypeScriptMITcommit fcb7747c7a01

TypeScript, MIT licensed. The project labels itself: ai, cli, copilot, developer tools, github copilot, multi agent and typescript.

squad runs. An Argusic agent installed it in 26 minutes and hit 6 errors on a clean machine with no GPU, and the whole session was recorded.

Squad CLI v0.13.1-build.3 builds from source, runs `version` and `--help`, and passes 3454+ tests across 128 test files on Node 22.13.0
What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 90 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 90 / 100
cost of the verifying run: $0.15 (measured)
recorded runs: 1
last tested: 2026-10-01
stars: 3,246
forks: 501
open issues: 128
watchers: 30
size: 27 MB
created: 2026-02-06
last push: 2026-10-01

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-01. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing squad, drawn from the recorded run — Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

Second `npm install` broke workspace resolution — replaced workspace symlinks with stale npm copies missing required SDK exports5 minutes
System Node.js v18.19.1 below project minimum >=22.5.02 minutes
npm internal error with Node v22.5.0 — packages require >=22.12 or >=22.18 (eslint, vite, cspell-lib)2 minutes
gh-aw-* tests fail — require `gh aw` CLI extension (`gh extension install github/gh-aw`) not available in this environment
repl-ux and layout-anchoring terminal spinner tests fail — require interactive PTY, non-interactive CI terminal cannot render spinner characters
resolution.test.ts fails due to test-model pollution from prior squad init run — personal squad config persists across runs

Install time: 26 minutes
Cold machine to finish: 27 minutes
Errors hit and fixed: 6 hit, 3 fixed with no human help
How the result was proved: npm run build exited 0 producing dist/; `node packages/squad-cli/dist/cli-entry.js version` returned '0.13.1-build.3'; `npm test` via vitest run on 128 selected test files passed 3454+ tests across config, agents, roles, tools, casting, capabilities, models, streaming, hooks, state, memory, telemetry, and engine modules
Model tokens used: 148,936
Exact commit tested: fcb7747c7a01
Container image: sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory: this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run: each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

exec
/bin/sh -lc 'export PATH="/tmp/node-v22.13.0-linux-x64/bin:$PATH" && cd /work/repo && echo "CLI ver…
 succeeded in 2120ms:
CLI version: 0.13.1-build.3
Test summary:
 Test Files  10 passed (10)
exec
/bin/sh -lc 'export PATH="/tmp/node-v22.13.0-linux-x64/bin:$PATH" && cd /work/repo && timeout 30 np…
 succeeded in 1954ms:
      Tests  406 passed (406)
tokens used
148,936

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

Reached a running state on a clean machine, with the session recorded.
Ran without a GPU, so it does not need one to start.
Licensed MIT, as reported by its host.

What did not, or is not known

Took 26 minutes to install, slower than the median of the 72 comparable projects Argusic has measured.
Hit 6 errors during setup, 3 of which were not solved.
Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 73 ai projects Argusic has installed and timed, squad was the 68th fastest to reach a running state, and 53 of 73 reached one at all.

What it is a reasonable choice for

Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	1/3	Runs	90.00	0.15	2026-10-01 13:43 UTC

Topics (from GitHub)

ai cli copilot developer-tools github-copilot multi-agent typescript

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/squad.svg)](https://argusic.com/subject/squad)

Questions

Does squad run?: Yes. squad runs. Argusic installed and launched it on a clean machine in 26 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test squad?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit fcb7747c7a01. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test squad?: The run that produced this verdict cost $0.15: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does squad take to install?: 26 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does squad need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing squad?: 6 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does squad compare with the alternatives?: Of the 73 ai projects Argusic has installed and timed, squad was the 68th fastest to reach a running state, and 53 of 73 reached one at all.
Where is the evidence for squad?: The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.