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
Tab switching shortcuts can't be unassigned in web (⌘1–9 still switch OpenCode tabs) #51349
The "Go to tab N" (mod+1–9) and previous/next tab (Ctrl+Tab, mod+Opt+←/→) shortcuts don't appear in Settings > Shortcuts because they're registered with an empty title. You can't unassign them, so they keep overriding the browser's own tab shortcuts. Unassigning "Open Project {number}" doesn't free ⌘1, because the tab shortcut is also bound to it.
Plugins
No response
OpenCode version
v1.18.31
Steps to reproduce
Open OpenCode web and open at least one tab.
In Settings > Shortcuts, unassign every "Open Project {number}" shortcut.
Press ⌘1. It switches to the first OpenCode tab instead of the first browser tab.
Search Settings > Shortcuts for a tab shortcut. There isn't one.
This issue might be a duplicate of existing issues. Please check:
[FEATURE]:tab shortcuts #37077: Requests tab-switching shortcuts, including Ctrl+Tab; its discussion also asks for configurable next/previous tab shortcuts. This report focuses on existing tab shortcuts being hidden from web Settings > Shortcuts and therefore impossible to unassign.
For keybind-related issues, please also check our pinned keybinds documentation: #4997
Activity
github-actions commentedon Sep 25, 2026
This issue might be a duplicate of existing issues. Please check:
For keybind-related issues, please also check our pinned keybinds documentation: #4997
thdxr commentedon Oct 11, 2026
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (
opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊