{"version":"2.1.304","anchor":"remote-control-eligibility-skips-token-scope-and-organizatio","canonical_anchor":"remote-control-eligibility-skips-token-scope-and-organizatio","heading":"Remote Control can skip its login-scope and organization checks in some cases","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/remote-control-eligibility-skips-token-scope-and-organizatio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Remote Control can skip its login-scope and organization checks in some cases\n\nIn some cases Remote Control no longer requires a full-scope login token or passes the organization check before it can be used\n\n**Unclear.** Which sessions qualify to skip these checks is not known.\n\n**What**\n\nRemote Control lets you drive a Claude Code session from another device. Before, Claude Code always required two things before allowing it: a full-scope login token, meaning a sign-in with full permissions, and a passing organization check. Now, in some cases, Claude Code skips both checks.\n\n**Why**\n\nSome sessions can now use Remote Control with a limited sign-in where they would previously have been refused with \"Remote Control requires a full-scope login token.\"\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}