Claude Code v2.1.223 ·
Invalid config dialog is now awaited before returning
A broken config file now holds the startup dialog until you dismiss it instead of racing past.
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
ConfigurationArea: what it touches
Bug FixesKind: in v2.1.223,
Bug FixesSection of the release
What
When a configuration file fails to parse at startup, the process waits for the dialog to be dismissed instead of continuing past it.
Details
- The startup handler previously returned the dialog promise directly; it now awaits
showInvalidConfigDialog and then returns. - The non-interactive path is unchanged: it writes "Configuration error in " to stderr and exits 1.
Evidence
Configuration error in
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.223 →
