{"version":"2.1.224","anchor":"remote-bridge-peers-documented-as-reply-only","canonical_anchor":"remote-bridge-peers-documented-as-reply-only","heading":"Remote bridge peers documented as reply-only","tier":"soon","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/remote-bridge-peers-documented-as-reply-only","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Remote bridge peers documented as reply-only\n\nRemote bridge sessions are described as reply-only and unreachable by name.\n\n**What**\n\nThe tool that lists other agent sessions now describes remote bridge sessions as ones you can only reply to, and states that no connector can reach them by name. This wording is only reachable when the cross-session feature is on, via the `tengu_harbor_kite` server flag or `CLAUDE_CODE_HARBOR_KITE`.\n\n**Evidence**\n\n`reply-only`\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: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}