Repository navigation
[FEATURE]: Missing key commands ought not be fatal errors. #6397
Description
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.
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Dec 29, 2025
For keybind-related issues, please also check our pinned keybinds documentation: #4997
github-actions commentedon Dec 29, 2025
This issue appears related to broader configuration error handling. Please check these potentially related issues:
Feel free to ignore if your specific case differs from these!
thdxr commentedon Mar 25, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.