Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PermissionsArea: what it touches
Internal ChangesKind: in v2.1.269,
Internal ChangesSection of the release
What
Claude 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.
Why
This 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.
Read from
Names in the bundleallow_remote_controlallow_remote_sessionsallow_claude_browser_extension
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up allow_remote_sessions, on Error reference.Your organization's `allow_remote_sessions` policy is off, so [Claude Code on the web](/docs/en/claude-code-on-the-web) and the commands that use it aren't available:errorssee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up allow_remote_sessions, on Error reference.
