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.232 ·

Cross-session message results now describe and pin the target

Cross-session send results now name the recipient and warn about duplicate or reused names.

Nothing to try yet In Development
JSON All of v2.1.232
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Cross-Session MessagingArea: what it touches
In DevelopmentKind: in v2.1.232,
In DevelopmentSection of the release

Richer send-result notes live in the cross-session messaging path, which is gated off by default.

What

Results from sending a message to another session now append a note identifying the recipient, with different wording for cloud and Remote Control targets, a caveat that cloud targets are one-way, and a warning when another session on this machine claims the same name or when a name was previously used by a different session. The resolved target is pinned into app state, and a separate short string is carried for display.

Details
  • One warning reads "Note: messaging a new session for the first time under a previously used name (was it restarted?)".
  • Gated by tengu_harbor_kite, which falls back to off, or the CLAUDE_CODE_HARBOR_KITE environment variable.
Evidence

Note: messaging a new session for the first time under a previously used name (was it restarted?)

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

Read from
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.232: 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.232. 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.232 →

Feedback