What
When Claude Code reads the legacy remoteControlAtStartup and autoUploadSessions settings from ~/.claude.json, it now checks each value against a schema before using it. If a value is invalid, it's dropped (treated as off or unset) and a one-time warning is logged for that key, rather than the raw value being trusted as-is.
Why
This stops a corrupted or malformed value in a legacy config file from silently causing unexpected behavior, and tells you when that happens instead of failing quietly.
Names in the bundleremoteControlAtStartupautoUploadSessions
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up remoteControlAtStartup, on All settings.
| [`remoteControlAtStartup`](#remotecontrolatstartup) | Connect [Remote Control](/docs/en/remote-control#enable-remote-control-for-all-sessions) automatically when a session starts | Remote, desktop, and notifications | Any file |settings-reference see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up remoteControlAtStartup, on All settings.
Anthropic's release notes agree
Fixed /config crashing and some on/off preferences being misread when a preference that has moved to settings.json still holds a value like…