Repository navigation
[Feature]: Improve visibility of key bindings #1044
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I am describing a concrete problem or use case, not just a vague idea.
Area
apps/web
Problem or use case
Currently, key bindings are only accessible via settings, which makes them easy to overlook.
Proposed solution
I'd like to propose adding a dedicated "Shortcuts" button to the top navigation bar that opens a dialog showing all available key bindings, with the ability to edit or reset them to defaults.
I've put together a rough proof-of-concept in a fork - screenshot attached.
Why this matters
It's much faster to navigate around with key bindings for many users.
Smallest useful scope
Add a button to the top navigation that displays the current set of key bindings. Additional scope to allow them to be modified.
Alternatives considered
No response
Risks or tradeoffs
No response
Examples or references
No response
Contribution
- I would be open to helping implement this.
Activity
juliusmarminge commentedon Jun 20, 2026
Keybindings now have a dedicated editable and resettable settings section and are surfaced in the command palette and contextual shortcut labels. Adding another permanent top-nav button would duplicate that UI.
This was closed as part of a large repo-wide maintenance sweep. If you think it's still relevant, please reopen.
Merge pull request #5 from Tevin2119/delivery/1044-a-duplicated-atten…