{"version":"2.1.273","anchor":"new-tool-fetchinboxmessage-remote-control-session-inbox","canonical_anchor":"new-tool-fetchinboxmessage-remote-control-session-inbox","heading":"Remote Control sessions can fetch messages from a session inbox","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/new-tool-fetchinboxmessage-remote-control-session-inbox","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Remote Control sessions can fetch messages from a session inbox\n\nA new FetchInboxMessage tool lets Remote Control sessions actually read inbox messages instead of always failing\n\n**What**\n\nRemote Control sessions previously received a `feature_disabled` failure whenever they tried to fetch a message from a session's \"inbox\". This is now a real feature:\n\n- A new tool, `FetchInboxMessage`, reads a single message from a session's inbox by `file_id`. It's used when a session receives a `session-inbox` notification, for example a message relayed from a linked Slack\/Teams\/chat thread or the Claude Code project thread.\n\n- The underlying handler now performs the real work: it re-checks whether the session owner has changed, refreshes the auth token if needed, and fetches the message using the session id, file id, base URL, and access\/trusted-device tokens.\n\nThe returned message is wrapped with trust markers. Only messages whose outer envelope is marked `from=\"rc_owner\"` are treated as the user's own request; everything else is explicitly untrusted third-party text that must not be acted on without checking with the user first.\n\n**Why**\n\nThis lets Remote Control sessions actually retrieve inbox messages relayed from other chat surfaces, while keeping a clear boundary between the user's own instructions and third-party text so the assistant doesn't act on untrusted content by mistake.\n\n- Area: Remote Control\n- Names: `FetchInboxMessage`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}