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

Claude Code v2.1.238 ·

Cross-session peer identity is now keyed to the account, still off by default

Session-to-session messaging identity now follows your account, but the whole feature is off by default.

Nothing to try yet Notable No documentation found In Development
JSON All of v2.1.238
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.238,
What probably matters to youSection of the release

Peer identity derives from host plus credential and recomputes on account change, needing CLAUDE_CODE_HARBOR_KITE or a flag that falls back to false.

What

Identity for talking to other sessions is now derived from the host plus the current credential (account and organization ids, or a fingerprint of the bearer token) and recomputed when the account changes. This sits under cross-session messaging, whose compiled fallback is false: it needs CLAUDE_CODE_HARBOR_KITE set, or the tengu_harbor_kite flag on, and on Windows also tengu_harbor_kite_win, which also falls back to false.

Details
  • A supervised child handed an identity that fails the safety check logs a refusal and gets no Remote Control identity at all.
  • The REPL reports its own cross_session_inbound availability as session metadata.
Evidence

cross_session_inbound

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.238: off

tengu_harbor_kite_win Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.238: off

Read once, for one account on one subscription tier, against v2.1.238. 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 →

See this entry in the whole of v2.1.238 →

Feedback