Unclear Whether this feature is active for a given user is unread, since the gate tengu_cozy_pixel has no recorded reading.
What
- A new control-request subtype,
fork_conversation, lets a host or SDK client fork the current session's conversation — optionally truncated to a specific target message — into a brand-new session created via the SDK backend, seeded with the prior message history and tagged for provenance verification. - Remote Control gains a
fork_conversationtool implementing this: it can fork from a specific message (target_message_uuid) or the whole transcript, writes a size-capped JSON "seed" file to disk, and uploads/attaches it to the newly created session, which can adopt, discard, or re-verify that seed on session start. - Failure cases are surfaced with specific reasons: "turn running", "commands queued", "prompt pending", "target not found", "history suppressed".
Why This lets you branch a conversation into a separate session (for example, to explore an alternative direction without losing the original), whether you're driving Claude Code through the SDK or through Remote Control.
Names in the bundlefork_conversation
Feature flag
tengu_cozy_pixel Not enough to sayNothing 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.268: off
Read once, for one account on one subscription tier, against v2.1.268. It isn't a statement about your account. What a flag value here can and cannot tell you
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Whether this feature is active for a given user is unread, since the gate `tengu_cozy_pixel` has no recorded reading.
The name it cites is new in this build
New in this build: tengu_cozy_pixel