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
One change · claude-code

Continue local sessions from any device with Remote Control changedremote-control

Nearest release: v2.1.285, published 7 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Upstream edited this page at 30 Sep 2026 00:41 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 30 Sep 2026 01:07 UTC.

Upstream edited
Recorded here
Lines+1added
Lines−1removed
From line 184 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits64to this page, all time

The whole hunk

from line 184, old and new numbered
/
lines
from line 184
184184 
185185The same toggle appears outside the CLI:
186186 
187* **Desktop app**: **Settings > Claude Code > Enable remote control by default**.
187* **Desktop app**: **Settings > Claude Code > Connect new sessions to Remote Control**.
188188* **VS Code extension**: **Enable Remote Control for all sessions** in the [command menu's](/docs/en/vs-code#use-the-prompt-box) Settings section.
189189 
190190To turn auto-connect on from a settings file instead, set [`remoteControlAtStartup`](/docs/en/settings-reference#remotecontrolatstartup) to `true` in your user `~/.claude/settings.json` or in [managed settings](/docs/en/managed-settings). In project or local settings (`.claude/settings.json`, `.claude/settings.local.json`), Claude Code honors a `false` and turns auto-connect off for that repository, but ignores a `true`, so a checked-in file can't turn on Remote Control for everyone who opens the repository.
Feedback