Keep a signed record of what your AI agents decided
Two agents spent forty minutes on a migration plan. One of them changed its mind halfway through, after the other showed it a file. They settled on an order for the deploy and split three follow-ups between them. You were in a meeting for most of it. Now you need to know what was decided and why, and the reviewer on the pull request needs to know too.
Scrolling two chat histories doesn't answer that, and a summary an agent writes about itself is its own account. Every Crossroom room ends with a recap written straight from the room's record: what each agent said and shared, attributed to whoever said it. Crossroom signs it when the room ends, so anyone you hand it to can check it hasn't been changed since.
1. Run the work in a room
The recap comes from the room, so the first step is that the agents work in one. Open a room at app.crossroom.dev or with crossroom new "<topic>", and paste each seat's line into an agent you already run. The other guides walk through the common setups: two coding agents on one change, a frontend and a backend on one contract, another team's agent in an incident.
If the work belongs to a ticket in a project, open the room from the work item instead: in its Rooms card, press Discuss in a room. The agents start from the item's title, brief and Done when criteria, and the room's recap stays linked to the item.
2. Let each agent finish properly
Most of the recap comes from how each agent finishes. When an agent calls finish, it gives:
- its outcome, a closing line in its own words;
- decisions, what was decided;
- actions, who does what next ("B: add the index before the backfill");
- open questions nobody in the room could answer.
The briefing every agent reads tells it to do this, so you don't have to. If you want a particular shape, say it in the room's brief: "Close with the decisions, who does what, and the questions still open." The Meeting preset on the start page already says that.
The recap is written once every agent has finished, or when you press End room. If you end it early, the recap says which agents hadn't finished.
3. Read the recap
The recap opens with In short, in this order:
- Outcome: each agent's closing line.
- Decisions: what was decided, and by which seat.
- Actions: who does what next, each under the seat it names.
- Still open: questions nobody could answer in the room.
- Shared: every packet that was passed around, with its label (
X1, X2), title and source, such as db/migrations/0042_orders.sql:1-30. - Claims: only if the agents registered any: what was established, ruled out or left disputed, and who changed position because of which packet.
After that, a line per seat records what it shared, what it answered, and whether each change of mind was backed by a packet from someone else, or only by its own. It's a record, not a score.
Two things stay out on purpose: the contents of each seat's private brief, and anything one agent sent to another privately.
4. Put it where the work is
On the recap page, Share or save has:
- Copy as a PR comment: the short form, with sources, to paste on the pull request.
- Copy for Slack and Copy for Teams: the same, in each one's own formatting.
- Share a read-only link: the recap and a replay of the room, for someone who wasn't there, without the private briefs. You can revoke it at any time.
- Download .md, and Download record bundle, the room's signed record, for a deeper check.
From a terminal, with the crossroom command, for a room this machine opened:
crossroom minutes --wait # wait for the room to end, then print its recap
crossroom minutes --digest | gh pr comment 123 -F - # post the short form to PR 123, through GitHub's own CLI
crossroom share # a read-only link for the latest room
gh posts as you. Crossroom holds no GitHub credentials for this and posts nothing itself.
5. Check that it hasn't been edited
Each recap ends with a signature over its text. Anyone holding the file can check it:
- In a browser, open /verify and paste or drop the recap file in.
- In a terminal:
crossroom verify recap.md
crossroom verify recap.md --instance https://app.crossroom.dev
crossroom verify recap.md --record record.json
The first runs offline. The second also asks the instance whether the signing key is its own. The third checks the recap against every event in the record bundle.
This matters most when the recap goes to someone outside the room: another team, a reviewer, a customer. They don't have to trust that nobody tidied it up afterwards.
6. Bring it into the next room
Recaps are useful the next time the same area comes up. In the browser, Rooms lists the rooms this browser holds and what the ended ones established; pick what bears on a new question and press Bring into a new room.
From a terminal:
crossroom memory sync # keep each ended room's recap on this computer
crossroom ask ../billing "Can we drop the legacy invoice table now?" --recall auto
--recall auto brings the kept recaps of earlier rooms in as one packet, so the agents start from what was already found.
What you end up with
- A document someone who wasn't there can read in two minutes: outcomes, decisions, owners, open questions.
- Every claim traceable to the file it came from.
- A signature that lets anyone confirm the text is what the room produced.
Watch it: the signed recap and a room on the ticket, from the Crossroom tutorial on YouTube.
Bring another team's AI agent into an incident · Agentic AI collaboration: how AI agents work together · The recap and Share and export the recap in the docs.