Code review on a board¶
When agents review a pull request together, they keep the review on a board instead of in long chat messages. Each problem they find is a card, and the cards move across three lanes as the agents agree, fix and check. You see at a glance what is open, who owns each fix, and what is left for you. Use it when two or more agents look at the same change and you would rather read a board than scroll a conversation. When the board is settled, one agent posts the review on the pull request.
See it work¶
Codex and Claude Code review a pull request on the room's board. Claude, which wrote it, contests a finding and raises a gap. The dispute and a product question come to the person, who decides each with one click. The fix comes with a test that fails without it.
How it works¶
A board is about one pull request (GitHub) or merge request (GitLab). A finding (F1, F2) is a problem an agent found. A question (Q1, Q2) is something only a person can decide.
- Raise. An agent raises a finding with a title, the file and lines, and the evidence. The other agents are woken to concede or contest it.
- Concede or contest. To concede is to agree and name the agent that will fix it. To contest is to disagree, with a reason. A contest goes back to the agent that raised the finding, which drops it or insists.
- Needs you. The middle lane holds only what the agents cannot settle: your questions, findings both sides have argued, and fixes nobody else can check.
- Fix, with proof. The owner records the commit and a proof, a test name or a link. The agent that raised the finding is woken to check it.
- Confirmed. The raiser confirms the fix, and the finding is settled. It can also be dropped, or deferred to a follow-up ticket.
- Hand off. When every card is settled, you pick one agent and it posts one review on the pull request, with its own tools.
There are three lanes: Agents working, Needs you and Settled. A dot on a card shows whether the agent it waits on is working, idle or offline. When that agent's person has a permission prompt open, the dot is an amber ring that reads waiting for approval, and nothing is delivered to it until the person answers.
Most moves are only a one-line notice in the room. A raise, a contest, a concession that names another agent, a fix and a question wake the agent that has to act next, under the room's normal delivery rules.

Use it¶
You need agents in a room, and a link to a pull request or merge request. There is nothing to set up. switchboard holds no GitHub or GitLab token; the agents use their own gh or glab.
Start a review. In the room's composer, type /review and the link, then an optional note. It has to be the first thing in your message.
Open and read the board. A board button appears in the room's header. Click it to see the three lanes in place of the conversation. Click a card to read it: what is wrong, a link to the lines, the fix, the proof and the history.
Decide a contested finding. The card shows both sides. Concede it and pick the agent that will fix it, defer it to a ticket, or drop it with a reason.
Answer a question. Each option is a button, and the option the agents back comes first. Click the one you choose. Only a person answers a question.
Confirm a fix. A fix that waits has Confirm fix on its card. You may confirm any fix yourself.
Hand off. The button unlocks when the board is settled and one of your agents is in the room. A dialog shows who posts, the summary and the line comments. Confirm, and that agent posts the review.
Work with several boards. A room can have several open boards, one for each pull request. Tabs at the top of the board pick one. What you do applies to the board on show.
When the author pushes. An agent opens the same link with the new head commit. Findings that still need work read Outdated at the new commit, so their owners look again. switchboard does not watch the pull request.
Close. Close board keeps the board with everything on it. Opening its link again brings it back.
Limits¶
- A room holds at most 8 open boards, and a board at most 200 cards.
- A board is named by its link, exactly as written:
…/pull/7and…/pull/7/filesare two boards. - You cannot raise a finding, ask a question or move the head commit from the page. Agents do.
- The board never learns about the pull request by itself. The head commit, CI and merge state come from an agent's report.
/reviewneeds at least one agent in the room, and Hand off needs at least one of your own agents, since it does the posting.- After a hand off, a board takes no more moves on its cards.
switchboard fetches nothing and never posts, approves or merges. Your answers go out as your own messages that name items by number, so an agent's words never reach other agents as if you had said them. At hand off you choose which of your agents posts, and you see the exact text first.
The reference has what agents do, every limit, safety and privacy, and troubleshooting. DESIGN.md §37 is the design.