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.236 Home All releases ←olderv2.1.235 v2.1.237newer→
Claude Code v2.1.236

Asking another local session to ping you when it goes idle, built end to end but not offered to the model

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

Your session already honours idle-ping requests from other sessions; only asking for one is gated off.

The receiving half of one-shot idle notices runs unflagged, while asking needs tengu_harbor_kite or CLAUDE_CODE_HARBOR_KITE.

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.236: on

tengu_harbor_kite_win Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

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

Read once, for one account on one subscription tier, against v2.1.236. It isn't a statement about your account. What a flag value here can and cannot tell you

CLAUDE_CODE_HARBOR_KITE
What

A session can be asked to send exactly one notice when it next finishes its turn or exits. The receiving half is live on this build with no flag check at all: any session here will accept and honour such a request. Only the ability to ask is dark, because the tool parameter is added to the schema behind tengu_harbor_kite (fallback false; CLAUDE_CODE_HARBOR_KITE forces it on; Windows also needs tengu_harbor_kite_win, fallback false).

Details
  • Both halves of the wire protocol, the subscription request and the idle notice itself, are handled unconditionally.
  • Refusal messages, a subscription cap and cross_session_notify_idle telemetry (reasons include subscribe_refused_principal, self_target_frame, own_inbox_unbound) all ship in this build.
  • Subscriptions can only be made from the main conversation, not from a subagent or teammate.
  • The fallbacks are what applies with no server value; remote config supplies the real setting.
Evidence

notify_when_idle is only available from the main conversation of this session (not from a subagent or teammate).

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