{"version":"2.1.301","anchor":"config-file-functions-no-longer-take-a-path-argument","canonical_anchor":"config-file-functions-no-longer-take-a-path-argument","heading":"Reorganised how Claude Code saves and backs up its main settings file","tier":"internal","area":"Config File","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/config-file-functions-no-longer-take-a-path-argument","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Reorganised how Claude Code saves and backs up its main settings file\n\nClaude Code now uses one queue to save its ~\/.claude.json settings file, and backs up a corrupted copy before it saves\n\n**What**\n\nClaude Code keeps its main settings in a file called `~\/.claude.json`. The code that reads, saves and backs up this file has been reorganised:\n\n- Every save now goes through one queue, instead of a separate queue for each file location.\n\n- Before saving, Claude Code can write a backup of a corrupted copy of the file and then make its usual backup.\n\n**Why**\n\nThis is mostly internal tidying. It touches how Claude Code handles a damaged settings file and the order in which saves happen, so those are the areas where any difference would show up.\n\n- Area: Config File\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}