Permission-mode stamping on cross-session idle notices sits behind tengu_harbor_kite_mode_emit, which falls back to false.
Messages sent between sessions on the same machine when one goes idle can now be stamped with the sending session's permission mode, as bypass or prompting. The stamping helper returns nothing unless the gate tengu_harbor_kite_mode_emit is on, and it falls back to false in this build, so no mode is attached.
- The mode comes from the inbound session's current permission mode, falling back to the mode recorded when the session was disconnected.
- The receiving side already reads this field on both idle notices and idle-notification requests.
- The same gate covered the notification-request case in 2.1.235; this extends it to idle notices.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_harbor_kite_mode_emit 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
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.