You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
PermissionsArea: what it touches
ImprovementsKind: in v2.1.222,
What probably matters to youSection of the release
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.
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeChanged Remote Control auto-start so repo-local settings (.claude/settings.json or .claude/settings.local.json) can no longer turn it on…
