Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.273 ·

Remote Control can fork a running conversation

A remote client can now ask Claude Code to fork the current conversation into a new branch, with a notice posted if it fails

Group of 2 You'll notice Nothing to try yet No documentation found In Development
JSON All of v2.1.273
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
In DevelopmentKind: in v2.1.273,
What probably matters to youSection of the release

What

  • A new fork_conversation bridge control request is now wired into the REPL for Remote Control sessions. It validates a target message UUID and title, then spawns a background fork of the current conversation, letting a remote client branch a running session mid-conversation.
  • If starting that fork fails, Claude Code now posts an informational/warning message into the newly forked session explaining that the fork could not be started.

Why

This lets remote clients branch an in-progress conversation without losing context, and makes sure the user still finds out if the fork didn't actually start.

Read from
Names in the bundlefork_conversation
Feature flag
tengu_cozy_pixel Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.273: off

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.273. It isn't a statement about your account. What a flag value here can and cannot tell you

See this entry in the whole of v2.1.273 →

Feedback