Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.286entry #17

Claude Code v2.1.286 ·

Remote Control disconnects when org policy starts refusing it, plus SDK bridge changes

Running Remote Control bridges now shut down with a notice when org policy refuses them; the SDK bridge can also switch SDK MCP servers on and off

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

Unclear What exactly makes the policy refuse Remote Control, and whether the watch is turned off in some modes, are not known.

What

Remote Control lets you drive a Claude Code session from somewhere else through a bridge, a connection that relays messages between the two. Claude Code now reacts when your organisation's policy changes while a bridge is running.

  • Both the standalone claude remote-control loop and the bridge inside an interactive session watch for org policy changes.
  • If policy now refuses Remote Control, the bridge shuts down or disconnects and shows a notice. The log line reads "Org policy now refuses the attached bridge".
  • The standalone loop also holds a session whose minimum version has not arrived yet, refreshes its settings from the server, and then admits or declines it.

The SDK bridge also changed. The SDK is the kit for driving Claude Code from your own program.

  • SDK MCP servers can be disabled and enabled through mcp_toggle. MCP servers are connectors that give Claude extra tools.
  • The logic that reconnects after signing in again was reworked.
  • The startup message (system/init) now includes messagesInView.

Why

Before, a policy change did not affect sessions that were already connected. Now, if your organisation turns off Remote Control, an active connection can end partway through, and a notice tells you why.

Read from
Names in the bundleclaude remote-control
What the documentation says
claude remote-control Claude Code changelog modified, high confidence * Fixed `claude remote-control --help` saying `--[no-]chrome` defaults to the machine's `/chrome` setting; spawned sessions keep Claude in Chrome off unless `--chrome` is passed see the edit
claude remote-control Let Claude coordinate ongoing work with Projects modified, high confidence * **In a terminal**: run `claude remote-control` in the folder and leave it running. In a git repository, add `--spawn worktree` to give each thread there its own [worktree](/docs/en/worktrees) instead of the folder itself. see the edit
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 claude remote-control, on Claude Code changelog. * Fixed `claude remote-control` failing to register behind an HTTP proxy with a misleading "Check your organization permissions" error (anthropics/claude-code#97352) 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 doubtWhat exactly makes the policy refuse Remote Control, and whether the watch is turned off in some modes, are not known.
Anthropic's documentation agreesclaude remote-control on Claude Code changelog
Anthropic's release notes agreeFixed Remote Control sessions (including claude remote-control) staying connected after your organization's policy turns Remote Control off…

See this entry in the whole of v2.1.286 →

Feedback