Follow Discord
Sweep 01 Oct 2026 · 17:27Z Build v2.1.287 508 read Stable v2.1.285 Latest v2.1.287 Next v2.1.287 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.286 ·

Organization policy blocks on remote features now come with a specific reason

A single check now matches Remote Control and cloud sessions to their organization policies and returns a clear message when one is turned off

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

Claude Code now has one check that takes a remote feature (Remote Control, a cloud session, or one it does not recognize) and looks up the organization policy that governs it: allow_remote_control or allow_remote_sessions. When access is refused, the check says whether data residency (where your organization's data must be kept) or a policy caused it, and gives a message such as:

  • Remote Control was turned off by your organization's policy.
  • Session mirroring was turned off by your organization's policy (allow_remote_sessions).
Why

If your organization has turned a remote feature off, you can be told which policy did it instead of just seeing it fail.

Read from
Names in the bundleallow_remote_controlallow_remote_sessions
What the documentation says
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 doubtIt is not clear which parts of Claude Code call this check.

See this entry in the whole of v2.1.286 →

Feedback