{"version":"2.1.283","anchor":"project-config-save-now-reports-whether-it-succeeded","canonical_anchor":"project-config-save-now-reports-whether-it-succeeded","heading":"Saving project config now reports whether the save worked","tier":"internal","area":"Configuration","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/project-config-save-now-reports-whether-it-succeeded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Saving project config now reports whether the save worked\n\nClaude Code's save of the current project's config now reports success or failure instead of returning nothing\n\n**Unclear.** Which parts of Claude Code act on the new success or failure result is not known.\n\n**What**\n\nClaude Code saves the current project's configuration while holding a lock, so two processes do not write at once. That save now reports whether it worked. It reports failure when:\n\n- the lock was lost partway through\n\n- re-reading the config was rejected\n\n- the write was refused because it would have lost your login details\n\n- the save was queued again after a crash marker\n\nIt reports success when the write went through or there was nothing to change. A lost lock is now caught and counted as a failure.\n\n**Why**\n\nOther parts of Claude Code can now tell when a config save quietly failed, including when the guard against losing login details refused to write.\n\n- Area: Configuration\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}