Repository navigation
Config Error on TUI is not readable like before #27056
Description
Description
Current Version of OpenCode the error printed to the terminal when you have an invalid configuration is not as helpful as it used to be, where it gave the file address and the part that is invalid.
This makes users not know where best to go to fix the issue.
Error: 4 of 5 requests failed: config.providers: ConfigInvalidError; provider.list: ConfigInvalidError; app.agents: ConfigInvalidError; config.get: ConfigInvalidError
at BO (/$bunfs/root/chunk-b69a2h84.js:469:644)
at <anonymous> (/$bunfs/root/chunk-b69a2h84.js:469:6060)
at processTicksAndRejections (native:7:39)Plugins
None
OpenCode version
1.14.48
Steps to reproduce
- Write an invalid Configuration
- Try to run the TUI for that directory
- Notice the error given
Screenshot and/or share link
No response
Operating System
macOS
Terminal
Ghostty
Reacted by Harrison Conlin
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon May 12, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is specifically about a regression (errors were more helpful in a previous version), please clarify that in the issue so maintainers can distinguish it from #17333.