Corrupt-config notices, including the restore command hint, now also appear from the repair path.
What's wrong with this entry?
The stderr notices for a missing configuration file and for an existing backup, including the "You can manually restore it by running: cp" hint, moved into shared builders and are now emitted by the storage-backed repair path too.
- That path writes a backup when a repair actually changed something, and reports the missing file when the storage layer says it is absent.
You can manually restore it by running: cp
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.223
Invalid config dialog is now awaited before returning
Both mention configuration
-
v2.1.228
Env vars set to an empty string now count as unset
Both mention configuration
-
v2.1.236
Reporting a corrupted config can no longer crash Claude Code
Both mention configuration