{"version":"2.1.236","anchor":"idle-notices-between-sessions-can-carry-the-sender-s-permiss","canonical_anchor":"idle-notices-between-sessions-can-carry-the-sender-s-permiss","heading":"Idle notices between sessions can carry the sender's permission mode, switched off here","tier":"soon","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/idle-notices-between-sessions-can-carry-the-sender-s-permiss","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Idle notices between sessions can carry the sender's permission mode, switched off here\n\nIdle notices could tell the other session whether you are in bypass mode, but that stamp is off.\n\n**What**\n\nMessages 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.\n\n**Details**\n\n- The mode comes from the inbound session's current permission mode, falling back to the mode recorded when the session was disconnected.\n- The receiving side already reads this field on both idle notices and idle-notification requests.\n- The same gate covered the notification-request case in 2.1.235; this extends it to idle notices.\n\n**Evidence**\n\n`tengu_harbor_kite_mode_emit`\n\n- Flag `tengu_harbor_kite_mode_emit`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.236; this account: on, anonymous baseline: on, compiled default: off)\n- Area: Cross-Session Messaging\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}