{"version":"2.1.232","anchor":"cloud-sessions-are-told-up-front-they-cannot-message-a-trust","canonical_anchor":"cloud-sessions-are-told-up-front-they-cannot-message-a-trust","heading":"Cloud sessions are told up front they cannot message a trusted-device peer","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/cloud-sessions-are-told-up-front-they-cannot-message-a-trust","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Cloud sessions are told up front they cannot message a trusted-device peer\n\nCloud sessions lacking a trusted-device token are told upfront they can't message a Remote Control peer.\n\n**What**\n\nIf you are in a cloud session with no trusted-device token and your organization requires one, sending a message to a Remote Control peer is refused immediately with an explanation, instead of being attempted and failing.\n\n**Details**\n\n- The message explains the target \"requires a trusted device, which a cloud session never has\" and tells you to message it from one of your own machines.\n- Applies when the session is remote (`CLAUDE_CODE_REMOTE`) and org policy requires a trusted device.\n\n**Evidence**\n\n`not reachable from a cloud session \\u2014 that session requires a trusted device, which a cloud session never has; message it from one of your own machines instead`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}