{"version":"2.1.63","anchor":"config-file-write-protection","canonical_anchor":"config-file-write-protection","heading":"Config File Write Protection","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.63\/e\/config-file-write-protection","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.63","markdown":"### Config File Write Protection\n\nA new safety mechanism prevents concurrent config writes from wiping authentication data in `~\/.claude.json`. Before writing, the system re-reads the file and refuses to proceed if the disk version is missing `oauthAccount` or `hasCompletedOnboarding` data that exists in the in-memory cache. This addresses a race condition reported in GitHub issue #3117.\n\n**Evidence**\n\nConfig lock function (search for `\"saveConfigWithLock\"`, `\"re-read config is missing auth that cache has\"`)"}