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

The message tool's notify_when_idle parameter and its supporting layer

Not switched on
Useful2 Signal4
Cross-Session Messaging Notable

Claude can ask another session to ping it when idle, but the parameter is hidden unless the gate is on.

The notify_when_idle parameter is only added to the message tool's schema when cross-session messaging is enabled.

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

notify_when_idle
What

The tool Claude uses to message another session on the same machine gained a notify_when_idle input that subscribes to a single notice when that session next goes idle or exits; sent without a message body it is a pure subscription. The parameter is only added to the tool schema when cross-session messaging is on, so with the gate off the model never sees it.

Details
  • Gate: CLAUDE_CODE_HARBOR_KITE environment variable, otherwise tengu_harbor_kite (fallback false), plus tengu_harbor_kite_win (fallback false) on Windows. Absent server config, invisible.
  • Refusal reasons each get their own sentence: no-inbox, self-target, peer-unsupported, unreachable-namespace, cap, peer-gone.
  • Subscriptions live in a table with a maximum size, eviction and expiry.
  • Sub-agents and teammates are refused, recorded as subscribe_refused_principal, under cross_session_notify_idle telemetry.
Evidence

Ask a session ON THIS MACHINE to send you ONE notice when it next goes idle

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.236 →