-
Notifications
You must be signed in to change notification settings - Fork 13.4k
0.119.0 crashes if config.toml is readonly #17593
Copy link
Copy link
Closed
Labels
bugSomething isn't workingSomething isn't workingconfigIssues involving config.toml, config keys, config merging, or config updatesIssues involving config.toml, config keys, config merging, or config updatesregressionBehaviors that worked in previous versions but were broken due to an updateBehaviors that worked in previous versions but were broken due to an update
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingconfigIssues involving config.toml, config keys, config merging, or config updatesIssues involving config.toml, config keys, config merging, or config updatesregressionBehaviors that worked in previous versions but were broken due to an updateBehaviors that worked in previous versions but were broken due to an update
Type
Fields
Give feedbackNo fields configured for issues without a type.
What version of Codex CLI is running?
codex-cli 0.119.0
What subscription do you have?
Plus
Which model were you using?
No response
What platform is your computer?
No response
What terminal emulator and version are you using (if applicable)?
No response
What issue are you seeing?
Starting with 0.119.0, if using a config.toml that is readonly, then on startup, after being asked if you trust the directory, codex crashes when trying to save to the config file.
The error given is
Error: thread/start failed during TUI bootstrapIn the logs, I see:
What steps can reproduce the bug?
What is the expected behavior?
Prior to 0.119.0, it would fail to persist the preference, but still continue and would be fully usable. I think that's better behavior in this case.
Additional information
No response