{"version":"2.1.314","anchor":"remote-control-policy-check-uses-remotecontrolpolicydeniedre","canonical_anchor":"remote-control-policy-check-uses-remotecontrolpolicydeniedre","heading":"Remote Control has its own policy check when started with --remote-control","tier":"internal","area":"Remote Control","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/remote-control-policy-check-uses-remotecontrolpolicydeniedre","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Remote Control has its own policy check when started with --remote-control\n\nWhen organization policy blocks Remote Control, starting with `--remote-control` now uses a dedicated check for the refusal message\n\n**What**\n\n`--remote-control` starts a session with Remote Control turned on, so you can also drive it from claude.ai or the Claude app. When an organization policy does not allow Remote Control, Claude Code refuses at startup. That refusal now comes from a check written for Remote Control, rather than from a general policy check with the message written inline.\n\n**Why**\n\nIf your organization blocks Remote Control, the wording of the message you see when it refuses may differ from before.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}