{"version":"2.1.229","anchor":"windows-now-has-its-own-gate-for-harbor-cross-session-messag","canonical_anchor":"windows-now-has-its-own-gate-for-harbor-cross-session-messag","heading":"Windows now has its own gate for Harbor cross-session messaging","tier":"use","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/windows-now-has-its-own-gate-for-harbor-cross-session-messag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Windows now has its own gate for Harbor cross-session messaging\n\nSetting CLAUDE_CODE_HARBOR_KITE forces cross-session messaging on, and Windows can now be allowed through.\n\n**What**\n\nThe check for Harbor cross-session messaging was rewritten. Setting `CLAUDE_CODE_HARBOR_KITE` now forces it on regardless of platform. Windows, which previously always returned false, is allowed through when the separate `tengu_harbor_kite_win` gate is on. The general gate is consulted last. Both gates fall back to off in this build, so unless the environment variable is set, whether it runs is decided by remote config.\n\n**Evidence**\n\n`tengu_harbor_kite_win`\n\n- Flag `tengu_harbor_kite_win`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.229; this account: on, anonymous baseline: on, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Cross-Session Messaging\n- Names: `CLAUDE_CODE_HARBOR_KITE`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 4\/5"}