Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.308 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.224 ·

Forked sessions can be told their original is still running

A forked session can be told its original is still running and how to message it.

Nothing to try yet No documentation found In Development
JSON All of v2.1.224
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Cross-Session MessagingArea: what it touches
In DevelopmentKind: in v2.1.224,
What probably matters to youSection of the release

The fork notice is disabled on Windows and otherwise gated off unless CLAUDE_CODE_HARBOR_KITE is set.

What

A new note injected into the conversation tells the model that this session is a copy of another session that is still running, when the copy was made, and how to find and message the original. It is off by default: the path is disabled on Windows and otherwise falls back to tengu_harbor_kite being false, so it only runs if remote config or CLAUDE_CODE_HARBOR_KITE turns it on.

Details
  • The note is wrapped in <fork-source> tags in the prompt.
  • Queued and pending prompts are checked first so the note is not added twice.
  • Logs fork_source_note, with a parent_gone outcome when the original session can no longer be found.
Evidence

This session began as a fork (copy) of another session that is still running:

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundleCLAUDE_CODE_HARBOR_KITE
Feature flag
tengu_harbor_kite Off by default, switched on for this account

The shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.

This account: on · anonymous baseline: on · compiled default in v2.1.224: 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.224. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns on for tengu_harbor_kite, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_harbor_kite, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_harbor_kite, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_harbor_kite, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_HARBOR_KITE

See this entry in the whole of v2.1.224 →

Feedback