{"version":"2.1.269","anchor":"new-permission-policy-name-mapping-for-remote-controlultrap","canonical_anchor":"new-permission-policy-name-mapping-for-remote-controlultrap","heading":"New permission-policy name mapping for remote-control\/ultraplan\/claude-in-chrome","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-permission-policy-name-mapping-for-remote-controlultrap","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New permission-policy name mapping for remote-control\/ultraplan\/claude-in-chrome\n\nRemote control, Ultraplan, and Claude-in-Chrome now map to named permission policies\n\n**What**\n\nClaude Code now has a lookup table connecting short feature names to the underlying permission policy that governs them: `remote-control` maps to `allow_remote_control`, `ultraplan` maps to `allow_remote_sessions`, and `claude-in-chrome` maps to `allow_claude_browser_extension`.\n\n**Why**\n\nThis builds on earlier work where org-policy denials for remote sessions and remote control started naming the specific policy responsible (`allow_remote_sessions` or `allow_remote_control`) when a flow was blocked. Having this explicit mapping makes it possible to consistently identify and report which policy is blocking a given feature, including for `claude-in-chrome`.\n\n- Area: Permissions\n- Names: `allow_remote_control`, `allow_remote_sessions`, `allow_claude_browser_extension`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}