{"version":"2.1.317","anchor":"config-save-fallback-no-longer-refuses-when-the-config-file","canonical_anchor":"config-save-fallback-no-longer-refuses-when-the-config-file","heading":"Saving project config no longer refuses when the config file is missing","tier":"notice","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/config-save-fallback-no-longer-refuses-when-the-config-file","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Saving project config no longer refuses when the config file is missing\n\nClaude Code no longer refuses to save its config just because the config file it re-read turned out to be missing\n\n**What**\n\nClaude Code keeps settings and sign-in details in a config file. Before saving, it can re-read that file. It refuses to write if the re-read version is missing sign-in details that Claude Code still has in memory, so it does not wipe them by accident.\n\nThat refusal is now skipped when the re-read found no file at all. Claude Code also now tracks an extra value related to saving when the disk is full.\n\n**Why**\n\nThis affects whether your sign-in details survive config saves when the config file is absent.\n\n- Area: Internals\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}