The Remote Control toggle in /config now shows as locked with a reason when your org policy disables it.
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.
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-settings see the edit
With `disableEssentialTelemetry`, `disableNonessentialTelemetry`, `disableNonessentialServices`, and `disableAutoUpdates` all set to `true`, the desktop application makes **no outbound connections to Anthropic-operated hosts at runtime**. …third-party/claude-desktop/telemetry see the edit
| `.mcp.json` | MCP servers bundled with this plugin. A JSON object keyed by server name: `{"mcpServers": {"<name>": {"type": "http", "url": "...", "oauth": true}}}`. A remote entry uses `type` (`http` or `sse`), not `transport`, and suppo…third-party/claude-desktop/extensions see the edit
Anthropic's documentation has since written up /config, on MCP, plugins, skills, and hooks.