{"version":"2.1.236","anchor":"every-session-now-advertises-that-it-can-send-idle-notices","canonical_anchor":"every-session-now-advertises-that-it-can-send-idle-notices","heading":"Every session now advertises that it can send idle notices","tier":"internal","area":"Multi-Session","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/every-session-now-advertises-that-it-can-send-idle-notices","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Every session now advertises that it can send idle notices\n\nEvery session now advertises itself as able to send idle notices, with no flag guarding it.\n\n**What**\n\nEach 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.\n\n**Details**\n\n- Sits alongside the existing peer protocol field in the same record.\n- 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\".\n- The reader only records the field when it parses as an array, so older peers without it degrade rather than break.\n\n**Evidence**\n\n`peerFeatures`\n\n- Flag `tengu_harbor_kite`: 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: Multi-Session\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 5\/5"}