Everyone at once
Send one message to every agent who can answer now. Replies arrive in the same thread, and an agent that can’t join is listed with the reason.
How it works
Follow a conversation through the room.
Five stops, from a first question to a change you can review and commit. Follow the example in order, or jump to a step. The scenes are re-created from the app, with a sample project.
- AskMessage one agent, or everyone in the room.
- Hand offAn agent asks another for help, and the answer comes back to it.
- ReviewAsk a second agent to review the plan before code changes.
- ApproveYou set each agent’s permission level and answer its requests.
- ChangeSee which files changed, then commit from the Git panel.
01Ask
Talk to one agent, or the whole room.
Choose who hears each message: one agent, two agents in a set conversation, or everyone in the room.
Pick who you’re talking to
Send to any agent in the room. Type @ to mention another one: ask Claude to check with @codex, and Claude can hand the question over.
Or start a room mode
With Claude and Codex connected, Debate, Brainstorm, Review and Build are fixed three-turn conversations between one lead and the other as peer. The first three are read-only; in Build, only the lead’s first turn can edit, using its existing edit permission.
Or ask the whole room
Choose Everyone, and each agent that can answer now replies separately.
One room per folder
Each project folder gets its own room, with its own history. Switch rooms from the sidebar.
02Hand off
Agents hand work to each other.
One agent can ask another for help, and the answer comes back to the one that asked.
One agent asks another
Here Claude asks Codex to review its plan. The ask appears in your thread, so you see who asked whom, and what.
Four automatic turns
By default a request gets four automatic turns, then waits for you to continue. With auto mode on, detected repeated handoffs or replies can make a request wait for you instead of receiving another automatic allowance.
Your allowance pays
Handoffs run on your own agent accounts and use your allowance. Turn limits bound turns, not dollars.
The answer comes back
The answer goes back to the agent that asked, here Claude, which carries on from there.
03Review
A second opinion before anyone writes code.
Ask one agent to check another’s plan, and see exactly what it found.
Codex reads the plan
Claude asks Codex to review its plan for CSV export. Codex reads the code and the project before it answers.
Points you can check
The review comes back as three concrete points, each about specific code: formula injection, the file’s encoding, and its size.
Thinking folds away
While an agent works, you can read the reasoning it shares. Once the reply starts, it folds into one line you can open again.
Advice, not proof
A review is advice. Still inspect and test the result yourself.
04Approve
You decide what runs.
Set how much each agent may do on its own, and answer what it asks.
Levels decide what asks
Read only: The agent is not allowed to edit. Ask first: Edits and actions requiring approval are shown to you. Commands a CLI treats as safe reads may run without an approval prompt.
Auto edits
Project edits may happen without individual approval. Commands and additional access still follow the provider’s approval rules.
Answer what it asks
The card shows the requested action and any location, extra access, reason or handoff origin the agent reports. Choose one of the answers shown. Some requests also offer a session answer.
Pause or stop
Pause holds new turns; a running turn may finish. Stop cancels the request and its follow-ups. Neither reverses changes or external actions already completed.
05Change
See exactly what changed.
Review the files and the diff, then commit when you’re ready.
Change cards and diffs
With One writer, the writer’s edits are recorded as a change card. Open it to see each file and its diff.
Agents decide, by default
More than one agent can edit, and they can overwrite each other’s changes. Crosstalk’s Undo is off in this mode, so use Git to inspect and restore work.
One writer, with Undo
Only the agent you pick edits the project. Undo restores eligible recorded file changes, not commands or their side effects. Windows only for now.
Commit from the Git panel
Commit with your own Git setup, put a task on its own branch, and open a pull request. Parallel tasks work in private copies (Windows only for now).
Also in the room
Built for busy rooms.
Ask everyone at once, run a task on the side, watch your usage, and pick up where you left off.
Project check
When you open a project, Crosstalk lists files that could steer an agent or run code, like instruction files, hooks and MCP settings, and shows what it does with each.
Usage
Token counts per agent and per request, plus each agent’s last ten minutes. Reported counts can be incomplete, so keep an eye on your provider’s usage too.
Parallel tasks
Give an agent a task to work on in a private copy of your project while the room carries on. Review the diff, then merge it or discard it. Needs a Git project.
Windows only for now
Restarts without surprises
After a restart, rooms reopen paused. A reply that may not have finished is shown for your review instead of being retried automatically.
Optional sync
Keep encrypted settings and room history in a private repository in your own GitHub account, and pick up on another computer. You sign in to your agents on each one.
Command palette
Press Ctrl+K (⌘K on a Mac) to search the actions available right now, from pausing the room to opening another folder.
Bring your agents into one room.
Early access for Windows and macOS. Get Claude Code and Codex ready to open your first room, then add the other supported agents through Setup.
Download CrosstalkYour first room
You’ll need your own agent accounts. Crosstalk doesn’t include model access.