Repository navigation
Unable to Exit OpenCode TUI When Configuration Errors Occur #4245
Description
Description
When OpenCode encounters a command or agent configuration error during startup, the TUI displays the error message but becomes unresponsive to normal exit commands. Users are unable to exit the application using standard methods and must resort to killing the process manually.
OpenCode version
1.0.61
Steps to reproduce
Create an invalid configuration in directory with incorrect command/agent settings
Launch OpenCode TUI with opencode
Observe that an error message is displayed
Attempt to exit using normal methods:
/exit, /quit, or /q commands
Ctrl+C interrupt
Notice that none of these methods work
Expected Behavior
When a configuration error occurs, OpenCode should either:
Validate configuration before launching the TUI and exit at the CLI level with an error message
Provide a functional exit mechanism even when in an error state
Respond to standard interrupt signals like Ctrl+C
Actual Behavior
The TUI enters an error state where it displays the configuration error but does not respond to any exit commands or keybindings. The terminal is taken over by the TUI, but the error handling logic does not provide a way to exit gracefully.
Workaround
Users must manually kill the OpenCode process:
kill <opencode-pid>
Suggested Fix
Consider adding early configuration validation before TUI initialization, or ensure that exit commands remain functional even when the application is in an error state.
Screenshot and/or share link
No response
Operating System
VM: Arch Linux（OpenCode 1.0.61）
Terminal
Host：Windows（Windows Terminal Version: 1.23.12811.0)
Activity
github-actions commentedon Nov 12, 2025
This issue might be a duplicate of existing issues. Please check:
opencode runand TUI exits hang on v0.15+ #3213: Similar TUI exit problems where /exit and Ctrl+C don't properly return control to shell, requiring manual process terminationThe common pattern across these issues is TUI becoming unresponsive to standard exit commands when in error states, requiring manual process termination.
Feel free to ignore if none of these address your specific case.
rekram1-node commentedon Nov 12, 2025
Your issue was made first but the newer one has more activity so im just gonna close this one and use the other one: #4246