Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ConfigurationArea: what it touches
Internal ChangesKind: in v2.1.283,
Internal ChangesSection of the release
Unclear Which parts of Claude Code act on the new success or failure result is not known.
What
Claude 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:
the lock was lost partway through
re-reading the config was rejected
the write was refused because it would have lost your login details
the save was queued again after a crash marker
It reports success when the write went through or there was nothing to change. A lost lock is now caught and counted as a failure.
Why
Other parts of Claude Code can now tell when a config save quietly failed, including when the guard against losing login details refused to write.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhich parts of Claude Code act on the new success or failure result is not known.
