Branching a conversation now keeps its REPL mode

When you branch a conversation with /branch, the new copy now keeps the original session's REPL mode instead of losing it

You'll noticeTier: how much it should matter to you

2Useful: my rating, 1 to 5

2Signal: worth watching, 1 to 5

SessionsArea: what it touches

ImprovementsKind: in v2.1.318, 03 Nov 26

ImprovementsSection of the release

What

A session is one conversation with Claude Code, saved so it can be resumed. Running /branch copies a conversation into a new session so you can try a different direction. If the session you branch from has REPL mode set, the new branch now keeps that setting. It is saved into the new session's history and applied when the branch opens. Before, a branch carried no REPL mode.

Why

A branched session no longer drops the REPL mode setting without telling you, so it behaves like the session it came from.

Read from

Names in the bundle/branch

See this entry in the whole of v2.1.318 →

The build it came inv2.1.318

3 Nov 2026 · 425 entries, this one is #100.

Use it now23
You'll notice215
Nothing to try yet27
Under the hood160

Either side of it

v2.1.317Older

Open the release →

Names in this entry

slash/branch
Create a branch of the current conversation at this point, so you can try a different direction without losing the conversation as it stands. Switches you into the branch and preserves the original, which you can return to with /resume. To run a copy as a separate background session instead of switching into it, use /fork; to hand a side task to a subagent that reports back into this conversation, use /subtask

Is this right?