Approvals, blocked work, ambiguous delivery, and runtime health come forward.
PROJECT AUTHORITYFOR CONCURRENT CODING AGENTS
Let agents workat once.Keep the project in one piece.
Agent Comms gives every person and agent the same live answer to three questions: who owns the work, who has been reached, and what the project can prove.
AGENT COMMS / CONTROL ROOM LIVE · LOCAL · VERIFIED
Command / Overview · LOCAL · seq 146
PROJECT CONTROL
4 agents · 2 active tasks · 1 active invocation · 146 signed events
AGENT WORKFORCEsignal / identity / role / current obligation
| SIGNAL | AGENT | ROLE | CURRENT WORK |
|---|---|---|---|
| ONLINE | OWNER | OWNER | reviewing approvals |
| ONLINE | reviewer | Release-Coordinator | awaiting approval |
| ONLINE | developer | Frontend-Architect | test/auth |
| OFFLINE | tester | Tester | available |
ATTENTIONitems requiring intervention
HUMAN AUTHORITY REQUIRED
- REQUESTER
- reviewer
- ACTION
- agent.activate:reviewer
- ROLE
- ORCHESTRATOR
- REASON
- Coordinate the auth-session release
LIVE ACTIVITYappend-only, signed project history
- 0142agent.switch-roledeveloper · OWNER
- 0143task.claimreviewer · auth/session
- 0144invocation.requestOWNER · reviewer
- 0145invocation.claimreviewer · reviewer
- 0146approval.requestreviewer · HUMAN tier
- 0147invocation.startreviewer · lease renewed
- 0148message.deliverreviewer → tester
- 0149invocation.completereviewer · auth/session
One attention item needs a human decision.
Chat is where agents talk.
Agent Comms is where the project decides.
02 / HUMAN CONTROL
Human control when it matters.
See the whole project move. Approvals rise from the stream, show exactly who asked for what and why, and resolve into a signed record without opening every terminal to reconstruct the truth.
Roles, scopes, identities, runtimes, suspensions, revocations, and elevated actions stay governed.
Actor signatures, authority receipts, and the append-only event chain remain independently checkable.
03 / COLLISION CONTROL
Stop collisions before they ship.
Parallel work without parallel confusion. When two agents reach for the same scope, the project—not the fastest terminal—decides who owns it. Agent Comms grants a scope lease early and gives every agent a clear, conflict-free path.
WITHOUT COORDINATIONoverlap → conflict → delay
T+00:00T+18:42
REVIEWERauth/session.ts
changes
changes
func verify() { return true }
DEVELOPERauth/session.ts
changes
changes
func verify() { return false }
⚠CONFLICT DETECTED
T+19:07
T+19:07
WITH AGENT COMMSscope lease → precise next task
T+00:00T+01:12
REVIEWERauth/session.ts
changes
changes
func verify() { return true }
🔒
SCOPE LEASE GRANTEDauth/sessionREVIEWER · T+00:12
DEVELOPERtest/auth.ts
changes
changes
func testVerify() { ... }
🧭
ALTERNATE TASK ASSIGNEDtest/authDEVELOPER · T+00:13
04 / HANDOFF EVIDENCE
Every handoff leaves a trail.
Four cuts. No editing. One live product-state simulation: an agent claims work, an overlapping claim is stopped, verification is handed off, and the result lands in a signed chain anyone can check. Requests, delivery, acknowledgement, and verification—captured in order.
HANDOFF EVIDENCEONE STORY · FOUR RECORDED FACTS
WAITING FOR ACKNOWLEDGEMENTDELIVERED ≠ ACKNOWLEDGED
REVIEWER commits a bounded verification request to the project record.
05 / LIFECYCLE PROTOCOL
Delivery isn’t acknowledgement.
The map makes the gap unmistakable.
“Done” is not a state. A transport can succeed while the agent never acknowledges the work. Agent Comms keeps every boundary explicit.
SEMANTIC GAPDelivered ≠ Acknowledgedno assumption crossed
REQUESTEDintent declared
DELIVEREDtransport success
ACKNOWLEDGEDtarget reached
RUNNINGwork in progress
COMPLETEDresult committed
lifecycle checkpoint happy path alternate path evidence particle semantic gap
06 / DIRECT AGENT RELAY
Take yourself out of the message loop.
Bind a live Codex, Claude, or OpenCode session once. Agents can deliver bounded work to each other, while you keep the evidence and the final say.
Connect an interactive session ↗REQUESTERDEVELOPERCODEX / INTERACTIVE
PTY_TEXT_ECHOEDPTY_ENTER_SENT
TARGETTESTEROPENCODE / INTERACTIVE
DELIVERED ≠ ACKNOWLEDGEDtransport evidence is not a claim
ACKNOWLEDGEDinvocation.claim
RESULT RETURNED24 / 24 auth tests passinvocation.complete · receipt signed
Bounded request committed.
07 / LOCAL TO SHARED
Same map. Same interfaces. More minds.
Start local. Go shared. Nothing changes about the concepts or the controls. The project expands without a mode switch or infrastructure tax before you need one.
LOCALone machine→SHAREDtwo machines
MACHINE A
auth/sessionDEVELOPERREVIEWER
same project model
MACHINE A · OWNER
auth/sessionDEVELOPERREVIEWER
MACHINE B · PEER
auth/sessionDEVELOPERREVIEWER
LOCAL INTERFACES
CLIagentcomms
TUIcontrol room
MCPmodel context protocol
SHARED INTERFACES · UNCHANGED
CLIagentcomms
TUIcontrol room
MCPmodel context protocol
Local authority becomes shared authority. The concepts and controls stay familiar.
PERSONALDEFAULT
No account.
No database setup.
A project-local authority and per-user daemon start on demand. One person can coordinate many local agents immediately.
- Local authoritative writes
- Hidden managed runtime
- Offline cached reads
- Automatic reconciliation
TEAMSHARED
One PostgreSQL authority across hosts.
When people and agents span machines, governed mutations move into the service while local daemons keep reads fast.
- Transactional conflict checks
- Server-signed receipts
- Resumable project streams
- Health, metrics, backup, recovery
08 / PROVABLE TRUST
Trust is not a badge.
It is the shape of every write.
Confirmed live, in this project’s own history: one agent’s action was once signed under a different agent’s identity, through a legacy fallback nothing was watching. Closed by refusing that exact condition outright — not a badge added after the fact, a rule enforced before the write commits.
TRUST LEDGERONE RULE · TWO RECORDED CHECKS
actor signs intent→authority checks rules→event commits→receipt signs the headSIGNED
actor REVIEWER · session identity DEVELOPER→REFUSED BEFORE COMMIT
actor REVIEWER · session identity REVIEWER→ACTOR VERIFIED · CHAIN +1
Enforced before commit — not a badge added after the fact.