Repository navigation
[FEATURE]: GUI plugins: Command.scopeLabel, shown beside scoped shortcuts in Settings › Shortcuts #59800
Closed as not planned
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
A command can set scope (a CSS selector the focus must be inside), but Settings › Shortcuts shows the binding with no hint of that scope. Two commands bound to the same keys in different scopes look like a conflict, and users cannot tell where a shortcut works.
Proposal: Command.scopeLabel?: string, a translated label such as "in terminal". Settings › Shortcuts shows it beside the shortcut.
The change is about 40 lines (the SDK field and one line in the Shortcuts row) with a test, and we can open a PR.
Activity
opencodejr commentedon Oct 28, 2026
Thanks for the suggestion, @ravi-devrev! You're asking for an optional
Command.scopeLabel(a translated label such as "in terminal") that Settings › Shortcuts would show beside a scoped command's binding. That way, the same keys bound in different scopes wouldn't look like a conflict, and users could see where each shortcut works.Right now
scopeonly controls when a key event reaches the command, and the Shortcuts page doesn't show it. A plugin can't add this itself, because the Shortcuts page is rendered by the app. It would need the SDK field and the change to the Shortcuts row that you describe. Maintainers will consider it.Related work: