You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
Internal ChangesKind: in v2.1.257,
ImprovementsSection of the release
The /config 'Enable Remote Control for all sessions' entry gained a locked variant: when kKt() (checking the managed setting disableRemoteControl) returns a reason, the setting is rendered as type: "managedEnum" with lock: { reason, source: _q() ? "managed" : "policy", writableWhileLocked: ["false"] } and a fixed value of "disabled". The gate controlling whether the setting shows at all changed from a single ch() check to _S() || _q().
The message 'Remote Control is disabled by your organization's policy (managed setting disableRemoteControl).' is now a shared constant reused by both the eligibility check and this new settings-panel lock logic, rather than being computed inline in two places.
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 disableRemoteControl, on Continue local sessions from any device with Remote Control.* **The error mentions `disableRemoteControl`**: your IT administrator has disabled Remote Control on this device through [managed settings](/docs/en/managed-settings), independent of the organization-wide toggle and of how you're signed i…remote-controlsee the edit
Added sinceA small documentation edit on Deploy managed settings touched a line naming disableRemoteControl after this was published.On Team and Enterprise plans, an Owner enables or disables [Remote Control](/docs/en/remote-control) and [cloud sessions](/docs/en/claude-code-on-the-web) organization-wide in [Claude Code admin settings](https://claude.ai/admin-settings/c…managed-settingssee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesA small documentation edit on Deploy managed settings touched a line naming disableRemoteControl after this was published.
