{"version":"2.1.224","anchor":"remote-control-sessions-now-explain-that-they-are-reply-only","canonical_anchor":"remote-control-sessions-now-explain-that-they-are-reply-only","heading":"Remote Control sessions now explain that they are reply-only","tier":"notice","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/remote-control-sessions-now-explain-that-they-are-reply-only","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Remote Control sessions now explain that they are reply-only\n\nMessaging a Remote Control session now explains it is reply-only until it messages you first.\n\n**What**\n\nSending a message or file to a name that matches a Remote Control session on your account no longer just fails. The tool now says such sessions are reply-only from here and can be messaged only after they message you first, and that the Remote send_message connector cannot reach these device-gated sessions. A hedged version of the message appears when the list of sessions could not be fetched.\n\n**Details**\n\n- The `ListAgents` tool now also advertises `ListPeers` as an alias.\n- The cross-device recipient schema variant behind this sits on the remote-config flag `tengu_harbor_kite`, whose fallback here is off, or the `CLAUDE_CODE_HARBOR_KITE` environment variable.\n\n**Evidence**\n\n`only in reply, after it messages you first`\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: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}