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
Search keybindings by pressing a shortcut to find existing assignments
#17510
In Settings → Keybindings, I want to find what a shortcut is assigned to by pressing that shortcut. This is especially useful before choosing a new binding: I know the key combination I want to use, but may not know the name of the command that already uses it.
The current search accepts text, including shortcut strings, but does not offer a way to capture a key combination for searching. Manually typing the shortcut syntax or scanning the list adds friction when checking which shortcuts are already taken.
Proposed behavior
Add an explicit “Record keys” or “Search by shortcut” mode beside the existing keybindings search:
Activate the mode, then press a combination such as Cmd+K on macOS or Ctrl+K on Windows/Linux.
Display the captured shortcut and filter the list to all bindings using that exact combination, including default and custom bindings in the selected settings scope.
Keep each matching command's “when” condition visible, so users can understand context-dependent reuse of the same shortcut.
Capture the combination for searching without running its normal T3 action or changing any binding.
Allow clearing or exiting capture mode and returning to normal text search. Show a clear empty result when no configured binding matches.
For example, recording Cmd+K would show the Command Palette binding and any other configured binding using Cmd+K. I could then inspect or edit the existing assignment before reusing it.
Why this matters
This would make it easier to discover existing shortcuts and avoid accidental conflicts while customizing keybindings. A shortcut can legitimately be shared under different conditions, so showing all matching assignments is more useful than a simple “already taken” message.
Alternatives / scope
Typing the shortcut into the existing search, inspecting conflict indicators while editing, or checking keybindings.json are alternatives. The requested improvement is a direct press-to-search workflow, without having to start editing a binding. Existing text search should remain available.
Search can cover T3's configured bindings; detecting shortcuts reserved by the OS or browser is outside this request. Some combinations may be intercepted before the app receives them.
Context and related discussion
Requested from the T3 Code Nightly desktop app on macOS, in Settings → Keybindings.
I searched existing issues and discussions and did not find a matching request.
Discussion #15312 concerns automatically focusing the keybindings text search. This request concerns capturing an actual shortcut to search for its assignments.
Posted in Ideas as directed by CONTRIBUTING.md and the repository's feature-request link.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Problem / use case
In Settings → Keybindings, I want to find what a shortcut is assigned to by pressing that shortcut. This is especially useful before choosing a new binding: I know the key combination I want to use, but may not know the name of the command that already uses it.
The current search accepts text, including shortcut strings, but does not offer a way to capture a key combination for searching. Manually typing the shortcut syntax or scanning the list adds friction when checking which shortcuts are already taken.
Proposed behavior
Add an explicit “Record keys” or “Search by shortcut” mode beside the existing keybindings search:
For example, recording Cmd+K would show the Command Palette binding and any other configured binding using Cmd+K. I could then inspect or edit the existing assignment before reusing it.
Why this matters
This would make it easier to discover existing shortcuts and avoid accidental conflicts while customizing keybindings. A shortcut can legitimately be shared under different conditions, so showing all matching assignments is more useful than a simple “already taken” message.
Alternatives / scope
Typing the shortcut into the existing search, inspecting conflict indicators while editing, or checking keybindings.json are alternatives. The requested improvement is a direct press-to-search workflow, without having to start editing a binding. Existing text search should remain available.
Search can cover T3's configured bindings; detecting shortcuts reserved by the OS or browser is outside this request. Some combinations may be intercepted before the app receives them.
Context and related discussion
Posted in Ideas as directed by CONTRIBUTING.md and the repository's feature-request link.
All reactions