Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.222 Home All releases ←olderv2.1.221 v2.1.223newer→
Claude Code v2.1.222

remoteControlAtStartup can no longer be turned on by repo-scoped settings

You'll notice
Useful4 Signal0
Permissions Notable

A cloned repo's settings can no longer switch on Remote Control at startup; only your own settings can.

remoteControlAtStartup
What

A checked-in project or local settings file can no longer enable Remote Control at startup, closing off a path where cloning a repo changed your startup behaviour.

Details
  • The setting is read through the security-sensitive settings path, so only user, policy or flag scope can enable it.
  • Project and local settings can still disable it: a false value wins.
  • A true value at repo scope is ignored and logged.
  • projectSettings is ignored entirely when it aliases user settings.
Evidence

repo-scoped settings cannot enable Remote Control; set it at user scope (/config)

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

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.222 →