{"version":"2.1.238","anchor":"cross-session-peer-identity-is-now-keyed-to-the-account-stil","canonical_anchor":"cross-session-peer-identity-is-now-keyed-to-the-account-stil","heading":"Cross-session peer identity is now keyed to the account, still off by default","tier":"soon","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/cross-session-peer-identity-is-now-keyed-to-the-account-stil","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Cross-session peer identity is now keyed to the account, still off by default\n\nSession-to-session messaging identity now follows your account, but the whole feature is off by default.\n\n**What**\n\nIdentity for talking to other sessions is now derived from the host plus the current credential (account and organization ids, or a fingerprint of the bearer token) and recomputed when the account changes. This sits under cross-session messaging, whose compiled fallback is false: it needs `CLAUDE_CODE_HARBOR_KITE` set, or the `tengu_harbor_kite` flag on, and on Windows also `tengu_harbor_kite_win`, which also falls back to false.\n\n**Details**\n\n- A supervised child handed an identity that fails the safety check logs a refusal and gets no Remote Control identity at all.\n- The REPL reports its own `cross_session_inbound` availability as session metadata.\n\n**Evidence**\n\n`cross_session_inbound`\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.238; this account: on, anonymous baseline: on, compiled default: off)\n- Flag `tengu_harbor_kite_win`: Off in both readings (read for one account on one subscription tier against v2.1.238; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Cross-Session Messaging\n- Names: `CLAUDE_CODE_HARBOR_KITE`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}