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

Claude Code v2.1.224 ·

Cross-session messaging inbox now actually starts at startup

Startup can now actually open the local socket that lets other sessions message you.

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
5Signal: 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

The inbox call site is filled in but gated behind CLAUDE_CODE_HARBOR_KITE and skipped on Windows.

What

Startup opens a local socket so other Claude Code sessions on the same machine can send this one messages. In the previous build the call site was empty. It is off unless the tengu_harbor_kite gate is on (in-source fallback false) or CLAUDE_CODE_HARBOR_KITE is set, and it never runs on Windows.

Details
  • Startup clears CLAUDE_CODE_MESSAGING_SOCKET and, unless a socket path was passed explicitly, uses the default path.
  • Success and failure are reported as agents_cross_session_inbox, with a bind_failed reason; setup time is recorded as setup_uds_messaging_ms.
  • Skipped with a log line on remote thin clients and when the gate is off.
Evidence

[uds-messaging] Skipped: cross-session messaging gate off

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