Project navigation and common creation actions currently require pointer use or repeated menu navigation. Advanced keyboard users need fast, memorable sequences that work consistently across project pages without conflicting with text entry.
Proposed behavior
Extend the existing command palette with a dedicated shortcut mode.
Press o outside an editable context to open the palette filtered to project navigation commands.
Press n outside an editable context to open the palette filtered to creation commands that are currently available to the user.
Show the valid continuation key beside every command.
Run a command immediately when its valid continuation key is pressed; Enter is not required.
For a nested group such as statistics, keep showing only valid continuations after the intermediate key.
Close shortcut mode on Escape, an unsupported key, or a short timeout. This mode is intended for advanced users and should reinforce valid key sequences.
Pressing Tab switches from shortcut-key handling to text search while retaining the current navigation-only or creation-only filter.
Opening the command palette normally via Ctrl/Cmd+k or the .command-palette button keeps its existing behavior. It displays shortcut sequences for discoverability, but typing those sequences there does not activate them.
Navigation sequences
Sequence
Destination
oo
Project overview
op
Pull requests
ou
Builds
og
Packages
ow
Workspaces
of
Files
oc
Commits
ob
Branches
ot
Tags
om
Code comments
od
Code compare
oi
Issue list
ok
Issue boards
oe
Iterations
osc
Code contribution statistics
osp
Pull request statistics
osi
Issue statistics
osb
Build statistics
Creation sequences
At minimum, support the requested eligible actions:
Sequence
Action
ni
Create an issue
np
Create a pull request
nt
Create a tag
nb
Run a build
Only show and activate a creation command when the corresponding project feature is available and the current user has permission. Unsupported sequences must not trigger an action.
Editable-context safety
Do not start or execute shortcut sequences while focus is in an editable or text-entry context, including text inputs, textareas, selectors, and content-editable/rich-editor components. After the user exits the editable context, shortcuts work normally.
Acceptance criteria
All listed navigation sequences route within the current project to the correct page.
o and n open visibly filtered shortcut modes with continuation keys displayed.
Valid continuation keys execute immediately.
Invalid keys, Escape, and the configured short timeout close shortcut mode without navigating or creating anything.
Tab enables text search without removing the active o or n group filter.
The normally invoked command palette displays shortcuts but does not interpret them as active sequences.
Creation entries follow existing feature-availability and permission checks.
Shortcut handling is disabled in all editable contexts.
The command palette/help documentation lists the supported sequences.
Existing command-palette keyboard and pointer behavior continues to work.
Problem
Project navigation and common creation actions currently require pointer use or repeated menu navigation. Advanced keyboard users need fast, memorable sequences that work consistently across project pages without conflicting with text entry.
Proposed behavior
Extend the existing command palette with a dedicated shortcut mode.
ooutside an editable context to open the palette filtered to project navigation commands.noutside an editable context to open the palette filtered to creation commands that are currently available to the user.kor the.command-palettebutton keeps its existing behavior. It displays shortcut sequences for discoverability, but typing those sequences there does not activate them.Navigation sequences
ooopouogowofocobotomodoiokoeoscosposiosbCreation sequences
At minimum, support the requested eligible actions:
ninpntnbOnly show and activate a creation command when the corresponding project feature is available and the current user has permission. Unsupported sequences must not trigger an action.
Editable-context safety
Do not start or execute shortcut sequences while focus is in an editable or text-entry context, including text inputs, textareas, selectors, and content-editable/rich-editor components. After the user exits the editable context, shortcuts work normally.
Acceptance criteria
oandnopen visibly filtered shortcut modes with continuation keys displayed.oorngroup filter.