{"version":"2.1.280","anchor":"legacy-global-config-values-validated-before-use-remotecont","canonical_anchor":"legacy-global-config-values-validated-before-use-remotecont","heading":"Legacy global config values validated before use (remoteControlAtStartup, autoUploadSessions)","tier":"notice","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/legacy-global-config-values-validated-before-use-remotecont","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Legacy global config values validated before use (remoteControlAtStartup, autoUploadSessions)\n\nLegacy remoteControlAtStartup and autoUploadSessions settings in ~\/.claude.json are now validated before use\n\n**What**\n\nWhen 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.\n\n**Why**\n\nThis 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.\n\n- Area: Settings\n- Names: `remoteControlAtStartup`, `autoUploadSessions`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}