{"version":"2.1.224","anchor":"cross-session-messaging-explains-why-it-is-unavailable","canonical_anchor":"cross-session-messaging-explains-why-it-is-unavailable","heading":"Cross-session messaging explains why it is unavailable","tier":"soon","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/cross-session-messaging-explains-why-it-is-unavailable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Cross-session messaging explains why it is unavailable\n\nMessaging another session now tells you why it failed instead of silently doing nothing.\n\n**What**\n\nSending a message to another session now returns a specific reason instead of quietly failing: one refusal when the feature is off in this session, another when a cross-machine send would have to route through Anthropic servers. Cross-session messaging is gated on `tengu_harbor_kite` (off by default) or the `CLAUDE_CODE_HARBOR_KITE` environment variable, and is off entirely on Windows.\n\n**Details**\n\n- The cross-machine route additionally requires a first-party provider and that nonessential traffic is not disabled; failing either gives the second refusal.\n\n**Evidence**\n\n`Cross-session messaging is not available in this session.`\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.224; 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: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}