{"version":"2.1.232","anchor":"cloud-sessions-can-be-addressed-as-message-targets","canonical_anchor":"cloud-sessions-can-be-addressed-as-message-targets","heading":"Cloud sessions can be addressed as message targets","tier":"soon","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/cloud-sessions-can-be-addressed-as-message-targets","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Cloud sessions can be addressed as message targets\n\nCloud sessions on your account can be message targets, but the enabling flag is off in this build.\n\n**What**\n\nClaude Code can now list the cloud sessions on your account and treat them as destinations for cross-session messages. It needs first-party login, the `allow_remote_sessions` capability on your account and an organization ID, plus either the `CLAUDE_CODE_HARBOR_KITE_CLOUD` environment variable or the `tengu_harbor_kite_cloud` remote flag, which is off in this build unless your server config turns it on.\n\n**Details**\n\n- Sessions come from the `\/v1\/code\/sessions` endpoint, fetched page by page and memoized for the process.\n- Archived sessions, bridge entries and placeholder \"husk\" records are filtered out of the list.\n- If the list cannot be fetched in time, the code says so rather than quietly returning a short list.\n\n**Evidence**\n\n`tengu_harbor_kite_cloud`\n\n- Flag `tengu_harbor_kite_cloud`: Off in both readings (read for one account on one subscription tier against v2.1.232; this account: off, anonymous baseline: off, 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_CLOUD`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}