{"version":"2.1.319","anchor":"remote-control-error-for-trusted-devices","canonical_anchor":"remote-control-error-for-trusted-devices","heading":"Remote Control can now refuse a session that needs a trusted device","tier":"notice","area":"Remote Control","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/remote-control-error-for-trusted-devices","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Remote Control can now refuse a session that needs a trusted device\n\nRemote Control now handles an organization policy that requires trusted devices, and tells you to run \/remote-control to start a new session\n\n**What**\n\nRemote Control lets you use a Claude Code session from claude.ai. Claude Code now recognises an error meaning the session's security level is below what your organization's policy requires.\n\nWhen that happens, Claude Code shows a message saying that trusted devices are now required, and tells you to run `\/remote-control` to start a new session.\n\n**Why**\n\nIf your organization sets a security policy for Remote Control, a session that does not meet it can be turned away. The message tells you how to get going again instead of leaving you with an unexplained failure.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}