Agent Fork
- Desktop, mobile and web
- All plans
What it does
Fork creates a second agent that already knows everything the first one knows: same role, same CLI, same model and the whole conversation (decisions taken, approaches ruled out, files already read). The two consoles then run in parallel on two separate conversations; the original never stops, slows down or sees anything. Use it to try a second approach without abandoning the first, or to get a twin to review a decision.
To ask a running agent one question without disturbing it, use Ask on the side instead (see Ask on the Side): same copy of the conversation, but in a bubble, with nothing persistent left behind.
Video (1 min 17): Agent Fork, shown in the real app. An agent finds a bug and lists four fixes, one click forks it, and the two twins follow two different fixes at the same time.
Where to find it
Hover an agent row that has an open session; the Fork button sits in its action bar, left of the ⋯ menu, which also carries Fork. The button only appears on an agent with a live session.
Fork from here (from a chosen answer): open the agent's conversation view, hover one of its answers and click the fork icon in the small row under it (next to copy and listen). The twin gets the conversation up to that answer, and nothing after it. Same button on the phone, under each agent answer of the conversation.
How to use it
- Click Fork on a running agent. A persistent twin is created and sorted in the list like any other agent (it survives closing the original).
- Its console opens. On Claude, Codex and Grok it already contains the whole conversation. On other CLIs a line on screen says this is a new session and that the previous conversation was written to a file the agent has been asked to read first.
- To branch from an earlier point, use Fork from here under an answer instead. The twin is always a fresh session handed the conversation up to that answer in a file (on every CLI, Claude included). It is told the later turns were left out on purpose, and that the project files were NOT rolled back: the original may already have changed them after that answer.
Settings
None.
Agent tools (MCP)
None. agents_spawn creates a blank agent with a brief, not a copy of a conversation.
Providers
- Native fork: Claude, Codex and Grok fork their own session. On Claude and Grok the twin is resumable from its first second. A Codex fork made on Windows cannot be resumed later (known gap).
- Fallback fork (every other CLI): the twin starts a fresh session and is handed a written record of the parent console; AgentsRoom says so on screen instead of degrading silently.
- Fork from here: available on every CLI that has a conversation view (Claude Code, Codex, Grok Build, Mistral Vibe, oh-my-pi, Antigravity CLI). Always the file road: no CLI can reopen an interactive session cut at a given message (Claude's hidden option for that only works in print mode).
Mobile
The whole fork of the agent row is not on the phone. Fork from here is: the fork icon under an agent answer of the conversation view asks the desktop to fork from that answer, then opens the twin.
Limits
- A fork runs on your own CLI account and spends your provider quota, unlike the Agent advisor which uses AgentsRoom's own allowance. It re-reads the whole context (largely served from cache on Claude).
- The fallback fork knows what was said in the console, not what the agent "had in mind" (no hidden reasoning is copied).
- Fork from here cuts the conversation, not your files: changes the original made after that answer are still in the project.
Common questions
- What is the difference with Duplicate? Duplicate and Flash duplicate copy the configuration only (role, CLI, model) and start from a blank page. Fork copies the conversation.
- Why is my fork not shown under its original agent? A fork is an independent agent that outlives its origin, so it sorts like any other agent. Only agents started by another agent (
agents_spawn) and QA Bots are nested under their parent (see Agent List Display and Filters). - Does the original agent notice? No. It carries on, undisturbed, and never sees the fork.
- Why is the Fork button missing? The agent has no open session. On CLIs without a fork command the only copy of the conversation is the console's scrollback, so a closed agent has nothing to fork.
- How do I ask my agent a question without interrupting it? Use Ask on the side, the round button at the bottom right of its pane: see Ask on the Side.
- Can I fork from an earlier message instead of the end? Yes: Fork from here, the fork icon under any answer of the conversation view, on desktop and mobile. The twin knows the conversation up to that answer only.
- Is there a video that shows it? Yes, a little over a minute, filmed in the real app: https://youtu.be/qmHq03adttM
Related
- Agent Morphing: change a running agent's role instead of duplicating it.
- Ask on the Side: ask a running agent one question on the side, without a second agent.
- Restore Session: how a forked session is resumed later.
- Multi-Provider Support: per-CLI capabilities.