{"version":"2.1.280","anchor":"remote-control-policy-denial-path-consolidated","canonical_anchor":"remote-control-policy-denial-path-consolidated","heading":"Remote Control policy-denial path consolidated","tier":"internal","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/remote-control-policy-denial-path-consolidated","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Remote Control policy-denial path consolidated\n\nRemote Control's org-policy-denial error handling was refactored to use a shared logging helper\n\n**What**\n\nWhen Remote Control (the feature that lets you control a Claude Code session from another device) is blocked by your organization's policy, Claude Code still shows the same \"Remote Control is disabled by your organization's policy.\" message. Internally, the code that handles this now goes through a shared helper which logs a `policy_denied` reason and flushes analytics, instead of separately importing an analytics-flushing function.\n\n**Why**\n\nThis is an internal cleanup of how the denial is logged and reported; it doesn't change what you see when Remote Control is blocked by policy.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}