Every session now advertises itself as able to send idle notices, with no flag guarding it.
tengu_harbor_kite On for this account, and not off by defaultThe 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
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
What's wrong with this entry?
Each running Claude Code writes a fixed one-element feature list into its entry in the local session registry, marking itself as able to send idle notices. This is written with no flag check, so builds shipping now become discoverable as idle-capable ahead of the user-facing half.
- Sits alongside the existing peer protocol field in the same record.
- The consumer is the subscribe path, gated behind
tengu_harbor_kite(fallback false), which refuses when the target does not advertise the feature and says "that session runs a version without idle notices". - The reader only records the field when it parses as an array, so older peers without it degrade rather than break.
peerFeatures
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.
-
v2.1.248
Wake routing and cross-session notices rewritten off UI effects
Both mention multi
-
v2.1.246
Multi-agent reply pairing now rejects and counts suspicious matches
Both mention multi
-
v2.1.239
Worker agents told to review, test, commit and report a PR link
Both mention multi