Skip to content

Commit 8d9659e

Browse files
bradygasterclaude
andauthored
docs(readme): show Squad in Claude Code with a recorded dashboard run (#2485)
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
1 parent 47082a8 commit 8d9659e

2 files changed

Lines changed: 12 additions & 0 deletions

File tree

‎README.md‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,18 @@ It's not a chatbot wearing hats. Each team member runs in its own context, reads
2020

2121
> **Responsible AI stance** — Squad is built to amplify a human operator with GitHub Copilot, not to remove humans from the loop. Use it to delegate faster, review better, and keep governance close to the code.
2222
23+
### See it in Claude Code
24+
25+
![Squad's team dashboard following a Claude Code session: the coordinator sends Dallas (Node.js engineer) to build a CLI and Parker (tester) to write tests at the same time, then Jordan (lead) reviews and Scribe records the decisions](docs/src/assets/images/squad-claude-dashboard.gif)
26+
27+
A real run, sped up 12×: a fresh repository, `squad init --client claude`, then two prompts to `claude --agent squad`. "Cast a small team" ran `squad cast` for a lead, an engineer and a tester in 50 seconds. "Team, build the MVP" sent the engineer and the tester out in parallel, then the lead reviewed. The result was a commit with 22 passing `node --test` tests, about $2.60 of model time for both prompts. The page is `squad dashboard`, which reads Claude Code's own session files and needs no setup.
28+
29+
```bash
30+
squad init --client claude
31+
claude --agent squad --mcp-config .mcp.json # "Cast a team for this repo", then give it work
32+
squad dashboard --open # watch the team in your browser
33+
```
34+
2335
---
2436

2537
## Quick Start
3.5 MB
Loading

0 commit comments

Comments
 (0)