Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.224 Home All releases ←olderv2.1.223 v2.1.225newer→
Claude Code v2.1.224

Cross-session messaging inbox now actually starts at startup

Not switched on
Useful3 Signal5
Cross-Session Messaging Notable not in their notes

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

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

Feature flag
tengu_harbor_kite On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

This account: on · anonymous baseline: on · compiled default in v2.1.224: on

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

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

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.224 →