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

Refusing peer messages when cross-session messaging is off is now a distinct case

Sending messages between your Claude sessions stays off, and refusals now name the kill switch explicitly.

Nothing to try yet No documentation found In Development
JSON All of v2.1.227
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.227,
In DevelopmentSection of the release

Cross-session messaging sits behind CLAUDE_CODE_HARBOR_KITE or a remote flag, off by default and never on Windows.

What

Cross-session messaging, which lets one Claude Code session send messages to another, stays off unless the tengu_harbor_kite remote flag (which falls back to off) or the CLAUDE_CODE_HARBOR_KITE environment variable is set, and it is never available on Windows. When it is off, inbound messages from other sessions are now refused as a kill switch rather than a generic refusal.

Details
  • The log says the message was refused because cross-session messaging is disabled, and telemetry records the cause as kill_switch instead of refused.
  • Messages already held for delivery are dropped with "gate off — dropped N parked peer message(s)" and receipted as expired rather than denied.
Evidence

cross-session messaging disabled (kill switch)

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.227: 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.227. 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.227 →

Feedback