anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-21 17:56:33 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[FEATURE] Add Ctrl+J/Ctrl+K navigation in menu bar (Vim-friendly) #4285

New Issue
Open
opened 2026-02-16 17:43:17 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 17:43:17 -05:00
Owner
Copy Link
Copy Source

Originally created by @muzig on GitHub (Jan 6, 2026).

Originally assigned to: @kommander on GitHub.

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

What do you want to change or add?
Add Vim-style keyboard navigation support to the project's menu bar (e.g., the "Commands" panel in the attached screenshot):

  • Bind Ctrl+K to move upward between menu options
  • Bind Ctrl+J to move downward between menu options

What are the benefits of implementing this?

  1. Improves efficiency for Vim developers: they can navigate menus without switching to mouse/other keys, keeping a keyboard-first workflow
  2. Enhances accessibility for a common developer group (Vim users), reducing friction when using the project's interface
Originally created by @muzig on GitHub (Jan 6, 2026). Originally assigned to: @kommander on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request What do you want to change or add? Add Vim-style keyboard navigation support to the project's menu bar (e.g., the "Commands" panel in the attached screenshot): - Bind `Ctrl+K` to **move upward** between menu options - Bind `Ctrl+J` to **move downward** between menu options What are the benefits of implementing this? 1. Improves efficiency for Vim developers: they can navigate menus without switching to mouse/other keys, keeping a keyboard-first workflow 2. Enhances accessibility for a common developer group (Vim users), reducing friction when using the project's interface
yindo added the opentuidiscussion labels 2026-02-16 17:43:17 -05:00
yindo commented 2026-02-16 17:43:17 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 6, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #4092: [FEATURE] Better navigation of output, alternative vim mode and non-blocking agent permission requests - includes discussion about vim-style navigation and command modes
  • #1764: [FEATURE] vim motions in input box - requests vim keyboard shortcuts in the prompt area
  • #6230: [FEATURE] Support multi-letter keybindings after leader key - related to vim-style keybinding namespaces

Feel free to ignore if none of these address your specific case.

For keybind-related issues, please also check our pinned keybinds documentation: #4997

@github-actions[bot] commented on GitHub (Jan 6, 2026): This issue might be a duplicate of existing issues. Please check: - #4092: [FEATURE] Better navigation of output, alternative vim mode and non-blocking agent permission requests - includes discussion about vim-style navigation and command modes - #1764: [FEATURE] vim motions in input box - requests vim keyboard shortcuts in the prompt area - #6230: [FEATURE] Support multi-letter keybindings after leader key - related to vim-style keybinding namespaces Feel free to ignore if none of these address your specific case. For keybind-related issues, please also check our pinned keybinds documentation: #4997
yindo commented 2026-02-16 17:43:18 -05:00
Author
Owner
Copy Link
Copy Source

@fengwk commented on GitHub (Jan 10, 2026):

Expected to get this feature

@fengwk commented on GitHub (Jan 10, 2026): Expected to get this feature
yindo commented 2026-02-16 17:43:18 -05:00
Author
Owner
Copy Link
Copy Source

@rafael-unloan commented on GitHub (Feb 15, 2026):

I would've thought you could implement via:

"keybinds": {
   "input_newline": "shift+return,ctrl+return,alt+return",
   "input_move_up": "ctrl+k",
   "input_move_down": "ctrl+j",
   "history_previous": "ctrl+j"
}

but nope. Why is this?

@rafael-unloan commented on GitHub (Feb 15, 2026): I would've thought you could implement via: ``` "keybinds": { "input_newline": "shift+return,ctrl+return,alt+return", "input_move_up": "ctrl+k", "input_move_down": "ctrl+j", "history_previous": "ctrl+j" } ``` but nope. Why is this?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label discussion opentui
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#4285
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?