Handoff stream
Every delegation with the exact brief that was passed, so you can see why a task moved.
You describe the work once, to the Scrum Master. It sizes the request and puts it on a Kanban board as cards. The Tech Lead, Developer and QA pick those cards up and finish them, and you watch each handoff in a live office and on the board.
First cd into your project folder, then run npx agenticsquad. Setup takes under 5 seconds.
You should not have to run a team of agents by hand. Talk to one routine and the team finishes the task.
Your session hands the request to the Scrum Master and only dispatches from there. It picks the platform team (Web, Android or iOS). A small change goes straight to that team's Developer with its Tech Lead reviewing; a bigger one goes to the Tech Lead, who writes the contract and brings in QA. Instructions, decisions and results live on the cards, so no one works from a pasted prompt.
Usually all of that is a scrolling terminal. AgenticSquad.dev reads the sessions your tools already record and shows who is working, on which card, what they handed off and why.
When the Scrum Master sizes a request as small (one to three files, no change to a shared type, API, payload or stored data), it skips the contract. One card goes straight to the platform's Developer (web-dev, android-dev or ios-dev), who maps the impact first, and that platform's Tech Lead reviews it.
Next to the floor plan and the board, the portal shows the conversation between agents, the tools they used, the code they changed and the time and tokens each role spent. A finished requirement can be replayed on the floor plan, and first-time users can watch a short demo.
Every delegation with the exact brief that was passed, so you can see why a task moved.
Which tools each agent reached for: terminal commands, MCP tools, handbacks and file writes, counted per call.
mcp__ tool is counted as MCP; write_to_file as Write.The diff each agent produced, filed under the card and the role that made it.
Work time is logged per role while it is active, with the token usage your tools recorded.
A Replay button on a finished requirement plays its handoffs on the floor plan, with decisions, reviews and results as captions. Save as video keeps a recording. Nothing is written to the board.
New to the office? A Watch demo button on the floor plan walks a scripted request through your own team, from the Scrum Master to the people who build and test it and back. It runs in the browser and saves nothing.
Roles, skills and rules live as plain Markdown and YAML in your repository, and Team Studio in the portal edits the same files. One command writes them out in the format each AI tool reads, including the rule that the main session only dispatches, so nothing drifts between tools.
The server listens on 127.0.0.1 and refuses requests from other websites, so a page you visit cannot read your board.
Jira and Confluence tokens are saved to a gitignored file readable only by you. The portal never displays them.
There is no mock data. Every card, handoff and token count comes from a real session, and 33 test suites guard it in CI. The Watch demo is labelled as a simulation and never touches your board.
The session you type into only dispatches work. In Claude Code a hook stops it from editing files, so every change, even a one-line fix, goes to the Scrum Master and gets reviewed.
Open your project folder in a terminal. New or existing, any stack.
Run the command from inside that folder: cd your-project, then npx agenticsquad. It takes under 5 seconds. The portal finds your agents, or helps you pick an Android, iOS or Web team (Scrum Master, Tech Lead, Developer and QA), or all three with the Scrum Master routing by platform, that you can adjust in Team Studio.
Ask as usual in Claude Code, Codex, Gemini or OpenCode. Your session hands the request to the Scrum Master, and the office fills in as your agents work.
New to it? Read the guide to running a multi-agent team in Claude Code.
AgenticSquad.dev gives your AI coding assistant a team: a Scrum Master plus a Tech Lead, Developer and QA for each platform (Web, Android, iOS). You talk to the Scrum Master, it puts the work on a Kanban board as cards, and the other agents pick the cards up and finish them. A local portal shows every handoff live on an office floor plan and on the board.
You need Node.js. Open a terminal, cd into your project folder, then run npx agenticsquad. There is nothing to install globally, and it takes under 5 seconds. The portal opens in your browser and finds your agents, or helps you pick a Web, Android or iOS team.
Claude Code, OpenAI Codex, Google Gemini and Antigravity, and OpenCode, including local models through OpenCode. You define the team once and npx -p agenticsquad agents sync writes it out as CLAUDE.md, AGENTS.md, GEMINI.md and each tool's own agent files.
No. The portal runs on 127.0.0.1 and reads each tool's session history from your own disk. Code, file paths, card text and tokens are never sent anywhere. The portal sends anonymous usage statistics, which you can switch off in Settings or by starting it with VO_ANALYTICS=off.
Yes. AgenticSquad.dev is free and MIT licensed.
Yes. Edit them in Team Studio inside the portal, or edit the Markdown files in .agents/definitions/ directly. You can set roles, names, allowed tools, skills, rules and avatars, then run npx -p agenticsquad agents sync.
The Scrum Master sizes each request. A small change (one to three files, no change to a shared type, API or stored data) goes straight to the platform's Developer, with the Tech Lead as reviewer. A bigger one goes to the Tech Lead, who writes technical contracts for the Developer and hands testing to QA.
Yes. Use npx agenticsquad --port 3001 for another port, or npx agenticsquad --dir /path/to/project to watch a different project. Several projects can run at once on different ports.