{"version":"2.1.299","anchor":"trusted-device-enrollment-skip-in-cloud-containers-and-reme","canonical_anchor":"trusted-device-enrollment-skip-in-cloud-containers-and-reme","heading":"Cloud sessions skip trusted-device enrollment and say clearly when Remote Control can't send","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/trusted-device-enrollment-skip-in-cloud-containers-and-reme","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Cloud sessions skip trusted-device enrollment and say clearly when Remote Control can't send\n\nWith `CLAUDE_CODE_REMOTE` set, Claude Code skips trusted-device enrollment and tells you nothing was sent to Remote Control targets\n\n**What**\n\nWhen the environment variable `CLAUDE_CODE_REMOTE` is set, which marks a session running in a cloud container, Claude Code no longer tries to enroll the machine as a trusted device. Before, enrollment ran whether or not the session was in the cloud.\n\nIn those cloud sessions, if Claude tries to send something to a Remote Control target (a device you control Claude Code from), it is told that the target cannot be reached without a trusted device and that it should tell you nothing was sent.\n\nSeparately, when enrollment happens because the server refused a request, Claude Code now remembers when that enrollment took place.\n\n**Why**\n\nIn a cloud session, sends to Remote Control targets fail, and Claude reports the failure to you instead of attempting enrollment in a container where it cannot work.\n\n- Area: Cloud Sessions\n- Names: `CLAUDE_CODE_REMOTE`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}