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
Ctrl+N and Ctrl+P should move the cursor up and down one line #4144
Ctrl+N and Ctrl+P are vital for navigating a buffer without having to use arrow keys, and should not be used for anything other than up and down. I suggest Ctrl+O as an available binding for the command pallet.
This issue might be a duplicate of existing issues. Please check:
Missing readline Ctrl+N and Ctrl+P #2176: Missing readline Ctrl+N and Ctrl+P - This issue specifically requests using Ctrl+N and Ctrl+P for readline up/down movements instead of next/previous message functionality
there's a lot of disagreement about what people want ctrl+n and ctrl+p to do we will add a dedicated vim mode to the buffer at some point but closing for now as we're unlikely to change the defaults here
Also, consider that while not everyone knows and uses every readline keybinding, most know some, and you can't predict which ones someone will know, so by disrespecting any except the most esoteric ones you're guaranteed to be making the input worse for some users.
Even macOS text inputs use ctrl+n and ctrl+p to move up and down. Go into any standard macOS text input and try typing ctrl+n/ctrl+p.
Activity
github-actions commentedon Nov 9, 2025
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
thdxr commentedon Nov 12, 2025
there's a lot of disagreement about what people want ctrl+n and ctrl+p to do
we will add a dedicated vim mode to the buffer at some point but closing for now as we're unlikely to change the defaults here
net commentedon Nov 12, 2025
At least please make it fixable via configuration. I don't see cursor up or cursor down keybinding here: https://opencode.ai/docs/keybinds/.
Also, consider that while not everyone knows and uses every readline keybinding, most know some, and you can't predict which ones someone will know, so by disrespecting any except the most esoteric ones you're guaranteed to be making the input worse for some users.
Even macOS text inputs use ctrl+n and ctrl+p to move up and down. Go into any standard macOS text input and try typing ctrl+n/ctrl+p.
net commentedon Dec 29, 2025
It's possible to configure this now.
{ "$schema": "https://opencode.ai/config.json", "keybinds": { "command_list": "ctrl+o", "input_move_up": "up,ctrl+p", "input_move_down": "down,ctrl+n" } }