Remote control startup now records where its on/off value came from, but nothing reads that yet.
The origin of the remote-control setting is computed at startup but no code in the build consumes it.
What's wrong with this entry?
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.
legacy_global_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.
-
v2.1.234
Startup prefetch failures no longer surface
Both mention startup
-
v2.1.239
Deleted working directories are detected at startup and handled during hooks
Both mention startup
-
v2.1.242
A socket path taken by another running Claude Code no longer breaks startup
Both mention startup