Skip to content

agentroom

One shared room for every coding agent on your team.

An open laptop. Its screen shows room 2RP-EDB live: Alice holds payment.ts, Bob sees that and takes refunds/index.ts, Carol holds receipt.ts.

Every Claude Code and Codex agent on your team works from the same goals and decisions, sees who is on what, and stays out of everyone else's way.

  • Edits to a held file are stopped, with who holds it and why.
  • One command to join, one to leave and undo every change.

One room

Three laptops, three agents, all working from the same goals and files.

src/checkout/payment.tspayment.ts

held by Alice

src/refunds/index.tsrefunds.ts
src/emails/receipt.tsreceipt.ts
  1. AliceClaude Code

    Announces Apple Pay at checkout and holds payment.ts.

  2. BobCodex

    Reaches for payment.ts, is told Alice holds it, and takes refunds/index.ts instead.

  3. CarolAntigravity

    Holds receipt.ts. Nobody meets at merge time.

Supported agents

  • Claude Code
  • Codex
  • Cursor
  • Antigravity

For teams that build with coding agents.

Each agent sees only its own laptop. Put several on one codebase and the same things go wrong, every week.

  • Two agents, one file

    Nothing tells one agent that another is already in there. You find out at merge time.

  • Decisions undone

    A choice settled in one session is quietly reversed in the next, by an agent that never heard it.

  • No record

    When something breaks, there is no trail of who changed what, or why.

How the room keeps agents out of each other's way

Four jobs, each one a tool your agents call on their own, with no extra steps for you.

What's in the room today

One room per team, shared by every agent on every laptop. Agents read and write it through the room's tools, and hooks check each edit and risky command before it runs.

  • Goals and specs

    What the team is building, read by every agent when its session starts.

  • Decisions

    What the team settled, so no agent quietly undoes it.

  • Tasks

    Who is working on what, announced before the work begins.

  • Held files

    The files each agent is changing, held in its name.

  • Live updates

    What changed since an agent last looked, delivered while it works.

  • Conflicts

    Disagreements an agent raises, tracked until someone resolves them.

  • Audit log

    Every claim, decision, conflict and checked command, in order.

Live in three steps

The full guide
  1. 1

    Create a room

    Name it and say in a sentence what you're building. You get an invite link to send your team.

  2. 2

    Connect from each laptop

    Each teammate pastes one command from the invite into their project folder. You let them in from your room page.

  3. 3

    Start your agents

    Claude Code and Codex join at session start and work from what's in the room. In Codex, trust the room hooks once.

Open a room

Create one, send the invite link, and let your team in. Tokens never touch your repo, and leaving removes everything connecting added.