Fork a session

Forking copies a conversation into a new session that starts with the full history of the original. Use it to try a second approach, to split one long session into two lines of work, or to experiment without risking a session that is going well. The original is left exactly as it was.

Agntree can fork Claude Code, Codex, opencode, and Pi sessions, either beside the original or into a new git worktree.

#Fork in the same worktree

Right-click a session and choose Fork Session Here.

A new session appears under the same worktree and opens in a terminal. It is named after the original with a number: forking Fix flaky cart test creates Fix flaky cart test (1). Both sessions share the same files, so use this when the two conversations will not edit the same code at the same time.

#Fork into a new worktree

Right-click a session and choose Fork Session to New Worktree…. Agntree asks for a branch name and a directory, then:

1. creates a new branch and worktree from the commit the source worktree is on,
2. copies the source worktree's uncommitted changes into it, including untracked files,
3. forks the conversation into the new worktree and opens it.

The fork starts from the same code and the same conversation as the original, in its own directory. The two agents can now work at the same time without touching each other's files, and you can compare the results as two branches.

The suggested directory is the same <repo>-worktrees/<branch> folder that Create Worktree uses.

#How each agent forks

Agntree uses the agent's own fork, so the result is a real session that you can also resume from the command line.

Claude Code writes nothing until the first prompt. If you close a Claude Code fork's terminal before sending one, Agntree removes the row: reopening it later would fork from wherever the original has moved on to, not from the point you chose.

#When to fork and when to start fresh

#Related

• Run multiple agents in parallel with git worktrees
• Sessions
• Worktrees and repositories