You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
The shortcut key for opening Settings is not working (Ctrl+,) #33740
Problem Summary: The keyboard shortcut for opening the Settings panel (Ctrl+,) does not trigger any action in OpenCode desktop version 1.17.10. This issue persists even after manually rebinding the command to other key combinations (e.g., Ctrl+Shift+S, Alt+S) – the new bindings also have no effect. All other keyboard shortcuts (e.g., Ctrl+P for command palette, Ctrl+S for save, Ctrl+Shift+E for explorer) work as expected.
Expected Behavior: Pressing Ctrl+, (or any user-assigned keybinding for the settings.open command) should open the Settings interface.
Actual Behavior: No response – no UI appears, no error messages are shown in the console or log files.
Steps to Reproduce:
Launch OpenCode desktop version 1.17.10 on Windows 11.
Open any project or the empty workspace.
Press the default shortcut Ctrl+, (Comma key) on the keyboard. Observe that nothing happens.
Open the Keyboard Shortcuts editor.
Search for the settings.open command and change its keybinding to, for example, Ctrl+Shift+S.
Save the changes and try the new shortcut. Observe that the Settings still does not open.
Try other default shortcuts (e.g., Ctrl+P, Ctrl+S) to confirm they are functional – they work without issue.
System Information:
Operating System: Windows 11 Pro, version 25H2 (Build 26200.8737)
OpenCode Version: 1.17.10 (Desktop application, not Web/VS Code Server)
Terminal/Shell: Not applicable – using the standalone desktop GUI app (no integrated terminal involvement).
Additional Context: I have already reviewed the pinned keybinding documentation (#4997) and confirmed that the default binding for settings.open is indeed Ctrl+, and that no conflicting keybindings are registered in my keybindings.json. I also tried resetting all keybindings to defaults and restarting the application – the issue remains.
Additional Notes: This issue is specific to the Settings command; other commands bound to similar shortcuts (e.g., Ctrl+Shift+P) work perfectly. I am happy to provide any further diagnostic info or test a debug build if that helps.
No issue template was used. Bug reports must include a Description field with details about the problem, steps to reproduce, and system information (OS, OpenCode version, terminal).
The current description is too minimal — please provide context such as what version you are using, your OS, and exact steps to reproduce the issue.
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
For keybind-related issues, please also check our pinned keybinds documentation: #4997
If you believe this was flagged incorrectly, please let a maintainer know.
changed the title [-]The shortcut key for opening Settings is not working[/-][+]The shortcut key for opening Settings is not working (Ctrl+,)[/+]on Jun 25, 2026
Thanks for updating the issue! It now includes all the required information — a clear problem description, steps to reproduce, and system details. The needs:compliance label has been removed.
Activity
github-actions commentedon Jun 25, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
For keybind-related issues, please also check our pinned keybinds documentation: #4997
If you believe this was flagged incorrectly, please let a maintainer know.
[-]The shortcut key for opening Settings is not working[/-][+]The shortcut key for opening Settings is not working (Ctrl+,)[/+]github-actions commentedon Jun 25, 2026
Thank you for updating the issue. Unfortunately it still doesn't meet our contributing guidelines.
What still needs to be fixed:
The current description is still too minimal to act on. A single sentence doesn't give enough context to investigate or reproduce the bug.
Please edit the issue to use the Bug Report template and fill in the required fields.
github-actions commentedon Jun 25, 2026
Thanks for updating the issue! It now includes all the required information — a clear problem description, steps to reproduce, and system details. The
needs:compliancelabel has been removed.github-actions commentedon Aug 24, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.