[FEATURE]: Missing key commands ought not be fatal errors. #3976

Open
opened 2026-02-16 17:42:09 -05:00 by yindo · 2 comments
Owner

Originally created by @ariane-emory on GitHub (Dec 29, 2025).

Originally assigned to: @rekram1-node on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Currently, if a user's configuration file has a keybinding for a non-existent command, it is a fatal error, preventing open code from starting up. This can be very inconvenient when working on features involving new key commands, as one has to switch configuration branches frequently to maintain compatibility with the code's branch.

Missing key commands ought to be a non-fatal error. Instead of just failing to start if a non-existent key command is used in a keybinding in the configuration, a more appropriate solution would be to start normally but bind the key to some function that displays a toast like "No command 'fake_command'" when the key is struck.

Originally created by @ariane-emory on GitHub (Dec 29, 2025). Originally assigned to: @rekram1-node on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request Currently, if a user's configuration file has a keybinding for a non-existent command, it is a fatal error, preventing open code from starting up. This can be very inconvenient when working on features involving new key commands, as one has to switch configuration branches frequently to maintain compatibility with the code's branch. Missing key commands ought to be a non-fatal error. Instead of just failing to start if a non-existent key command is used in a keybinding in the configuration, a more appropriate solution would be to start normally but bind the key to some function that displays a toast like `"No command 'fake_command'"` when the key is struck.
yindo added the opentuidiscussion labels 2026-02-16 17:42:09 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Dec 29, 2025):

For keybind-related issues, please also check our pinned keybinds documentation: #4997

@github-actions[bot] commented on GitHub (Dec 29, 2025): For keybind-related issues, please also check our pinned keybinds documentation: #4997
Author
Owner

@github-actions[bot] commented on GitHub (Dec 29, 2025):

This issue appears related to broader configuration error handling. Please check these potentially related issues:

  • #4245: Unable to Exit OpenCode TUI When Configuration Errors Occur - addresses graceful error handling during startup
  • #3537: Custom slash commands can crash opencode on startup - similar fatal error issue but for command syntax errors
  • #4850: Plugin syntax errors are handled poorly - related issue about non-fatal error handling in configs

Feel free to ignore if your specific case differs from these!

@github-actions[bot] commented on GitHub (Dec 29, 2025): This issue appears related to broader configuration error handling. Please check these potentially related issues: - #4245: Unable to Exit OpenCode TUI When Configuration Errors Occur - addresses graceful error handling during startup - #3537: Custom slash commands can crash opencode on startup - similar fatal error issue but for command syntax errors - #4850: Plugin syntax errors are handled poorly - related issue about non-fatal error handling in configs Feel free to ignore if your specific case differs from these!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#3976