A broken config file now holds the startup dialog until you dismiss it instead of racing past.
What's wrong with this entry?
When a configuration file fails to parse at startup, the process waits for the dialog to be dismissed instead of continuing past it.
- The startup handler previously returned the dialog promise directly; it now awaits
showInvalidConfigDialogand then returns. - The non-interactive path is unchanged: it writes "Configuration error in " to stderr and exits 1.
Configuration error in
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.228
Env vars set to an empty string now count as unset
Both mention configuration
-
v2.1.228
Config backup moved into a shared helper
Both mention configuration
-
v2.1.236
Reporting a corrupted config can no longer crash Claude Code
Both mention configuration