Four features for the moments when agents need a person, or each other: a Needs you list at the top of the dashboard, handoffs between teammates, a tool that lets an agent wait for a teammate's work, and a weekly digest for whoever runs the team.
Agents coordinate on their own most of the time. When they can't, the item lands in Needs you, at the top of the dashboard's Overview:
- override requests you're allowed to approve,
- edits a hook blocked,
- open conflicts that involve your work,
- messages you were asked to acknowledge,
- questions waiting for your answer.
Each row has its action right there. When a hook blocks Jordan's Codex from editing the protected src/auth/tokens.ts, Maya, an admin, sees a Blocked edit row from "Jordan · Codex" and can click Override… with a reason. The count shows as a badge on the Overview tab, and × hides an item for you only. See Needs a human.
Going on leave, or the work turned out to be someone else's? Hand an intent to a teammate. They become its owner, and their agent picks it up with everything yours knew: the plan, the claims, the files touched, open conflicts, the last status and your note. Three ways to do it:
Ask your agent: "hand this off to Jordan, the PDF layout is done but the totals are wrong".
From the CLI:
comity handoff @jordan --note "PDF layout is done; totals still wrong"
In the dashboard: open the intent in Work and click Hand off….
Jordan's agent sees Handed off to you at its next tool call or prompt, and takes over once he confirms. A direct thread opens between you two in Messages. See Handoffs.
When a teammate's agent holds something yours needs, your agent can call wait_for instead of editing around it. Jordan's agent needs src/billing/invoice.ts, which Maya's agent holds for INT-41. It waits on the intent:
{ "intent": "INT-41", "timeout_seconds": 50 }
When Maya's agent merges, the wait returns within about a second and Jordan's agent goes ahead. If time runs out, it learns who holds the file and can wait again, send a message or do something else. See Waiting with wait_for.
Once a week, the people who run the team get a summary of the last seven days: conflicts caught, estimated time saved, the most contended files and contracts, overrides, unanswered questions and one suggested next step. It posts to Slack and emails owners and admins who opt in. Turn it on in Integrations → Weekly digest, pick a day and hour (Monday 14:00 UTC by default), and use Preview to see it before it goes out. See Weekly digest.