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

SendMessage can address other sessions directly and reports delivery timing

Messages can be addressed to a specific session by socket or id, blocked unless peer messaging is enabled.

Nothing to try yet Notable No documentation found In Development
JSON All of v2.1.224
Nothing to try yetTier: how much it should matter to you
3Useful: 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

uds: and bridge: addressing plus delivery timing telemetry are validated off unless CLAUDE_CODE_HARBOR_KITE is set.

What

SendMessage can now target a peer by local socket (uds:) or by session id (bridge:), with failure advice that distinguishes a stale socket from a busy pipe, and it records a send_message_delivery event with the route taken and the time it took. Both address schemes are refused at validation time unless the peer feature is on, which needs tengu_harbor_kite or CLAUDE_CODE_HARBOR_KITE and a non-Windows machine.

Details
  • A socket that is gone (connection refused or missing) and a pipe that is busy produce different guidance.
  • The delivery event also carries how long the send waited when it was blocked.
  • With isolatePeerMachines on, sending to a cloud session now requires an explicit approval prompt.
Evidence

send_message_delivery

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
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's release notes agreeAdded cross-session SendMessage: Claude Code sessions can now message each other, on any of your machines, with ListAgents to discover them…
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