Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.317 ·

/remote-control can be disabled by managed policy and drops its upgrade prompt

Admins can block /remote-control through managed settings, its status message no longer carries an upgrade prompt, and a follow-on tip is switchable

Group of 2 You'll notice Improvements
JSON All of v2.1.317
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
ImprovementsKind: in v2.1.317,
ImprovementsSection of the release

Unclear Which managed setting disables /remote-control is not stated.

What

/remote-control (alias /rc) makes a session available for Remote Control from claude.ai.

  • The command can now be blocked by managed settings, which are settings an organisation pushes to its users. When that applies, the command check returns managed_disabled.
  • The status message shown while /remote-control is active no longer carries an upgradeNudge, so the upgrade prompt is gone from it.
  • The tip saying you can also drive this session from claude.ai/code or the mobile app now sits behind a remote switch, tengu_maple_rung. Nothing has been read about whether that switch is on.

Why

Enterprise admins can now turn off Remote Control for their users. Some users may also see one less upgrade prompt, and the follow-on tip may not appear for everyone.

Read from
Names in the bundle/remote-control/rc
Feature flag
tengu_maple_rung Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.317: off

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.317. It isn't a statement about your account. What a flag value here can and cannot tell you

Since it was published

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 since Anthropic's documentation has since written up /remote-control, on Claude Code changelog. * Fixed `/remote-control` showing a session as available after a failed connection changelog see the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhich managed setting disables /remote-control is not stated.
Anthropic's documentation agreesAnthropic's documentation has since written up /remote-control, on Claude Code changelog.
Anthropic's release notes agreeFixed /remote-control answering "Unknown command" instead of saying that Remote Control is turned off by the disableRemoteControl setting

See this entry in the whole of v2.1.317 →

Feedback