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
HomeReleasesv2.1.224entry #268

Claude Code v2.1.224 ·

Cross-session messaging explains why it is unavailable

Messaging another session now tells you why it failed instead of silently doing nothing.

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
3Signal: worth watching, 1 to 5
Cross-Session MessagingArea: what it touches
In DevelopmentKind: in v2.1.224,
In DevelopmentSection of the release

The refusal messages only surface once cross-session messaging is enabled, and it is off on Windows entirely.

What

Sending a message to another session now returns a specific reason instead of quietly failing: one refusal when the feature is off in this session, another when a cross-machine send would have to route through Anthropic servers. Cross-session messaging is gated on tengu_harbor_kite (off by default) or the CLAUDE_CODE_HARBOR_KITE environment variable, and is off entirely on Windows.

Details
  • The cross-machine route additionally requires a first-party provider and that nonessential traffic is not disabled; failing either gives the second refusal.
Evidence

Cross-session messaging is not available in this session.

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