Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.224 ·

Startup remote-control setting now tracks where its value came from

Remote control startup now records where its on/off value came from, but nothing reads that yet.

Under the hood Nothing to try yet Internal Changes
JSON All of v2.1.224
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
Internal ChangesKind: in v2.1.224,
What probably matters to youSection of the release

The origin of the remote-control setting is computed at startup but no code in the build consumes it.

What

Resolving whether remote control is on at startup now returns the origin of the value as well: managed policy, a command-line flag, user settings, an older global config value, a project or local setting turning it off, or nothing set. The warning that repo-scoped settings are ignored is unchanged. Nothing in the build was found reading the origin.

Evidence

legacy_global_config

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundleremoteControlAtStartup
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agree[VSCode] Fixed sessions not honoring remoteControlAtStartup when explicitly enabled

See this entry in the whole of v2.1.224 →

Feedback