Repository navigation
regression: Near-silent failure to start when convict file is bad #7521
Description
Description
When the configuration file is bad - for example, if it contains unknown keys, or unknown key commands in its keybindings - opencode, when run using bun dev, simply fails to start with no error other than error: script "dev" exited with code 1 instead of reporting a specific error as it used to. This error was introduced yesterday in commit adae0d185.
Sample bad opencode.json file:
{
"$schema": "https://opencode.ai/config.json",
"bad_setting": "i am a bad configuration file",
}
Plugins
None
OpenCode version
1.1.8
Steps to reproduce
- Use the configuration file above.
- Try to start opencode using
bun dev. - Observe that open code silently fails to start.
Screenshot and/or share link
No response
Operating System
MacOS Sequoia latest
Terminal
iTerm2
Activity
github-actions commentedon Jan 9, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
github-actions commentedon Jan 9, 2026
For keybind-related issues, please also check our pinned keybinds documentation: #4997
ariane-emory commentedon Jan 9, 2026
Resolved via #7522.