The receiving half of one-shot idle notices runs unflagged, while asking needs tengu_harbor_kite or CLAUDE_CODE_HARBOR_KITE.
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).
- 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_idletelemetry (reasons includesubscribe_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.
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.
tengu_harbor_kite Off by default, switched on for this accountThe 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.236: off
tengu_harbor_kite_win Off in both readingsThe 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: off
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
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.
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.
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.
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.
Added notify_when_idle to cross-session SendMessage: ask another Claude Code session on this machine to send one notice when it next goes…