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
[Bug] Home/End keys in input box scroll message list instead of moving cursor #27661
Currently, when typing in the input box, pressing the Home or End keys triggers the message list to scroll to the top or bottom, rather than moving the cursor to the beginning or end of the text line. This makes it very difficult to edit long messages.
Plugins
No response
OpenCode version
1.15.0
Steps to reproduce
Focus on the message input box.
Type a long sentence.
Press the Home key to try and return to the start of the sentence.
Observe that the message history scrolls to the top instead of the cursor moving.
Screenshot and/or share link
No response
Operating System
windows10
Terminal
Windows Terminal
Reacted by Grzegorz Blach, andrew-corlann, heguro, kna-makerx, Dmitry, Uwe Jugel, Theodore Brown, Santiago Favrin and Kyle Baker
Home/End have been std. keys for decades to jump to start/end in input boxes.
Please consider adding these as (additional) defaults. Windows/Linux users' typing muscles will benefit.
The current C-a and C-e defaults are dual-key bindings that are harder to type and reach, also because left Ctrl requires pinky finger, which may often feels unnatural.
I vote ➕ for this, since home/end text navigation is ubiquitous.
Reacted by Dmitry, Theodore Brown, Syndesi, Erich Yu, intensite, Kyle Baker, Isa and tchernomax
this really is a pain. jumping to the top of the conversation is not really a common thing to need, there's already a secondary obscure keybinding added for that for users who do want it, and home/end to jump around within text is standard muscle memory for programmers everywhere. it makes opencode feel like a very unserious product that isn't built by devs, for devs, to not respect that convention used literally everywhere inputs are used.
Reacted by Syndesi, Jason Dunham, George Mendoza, tchernomax, Theodore Brown, Jason Hills and Mike Kolesnik
Activity
github-actions commentedon May 15, 2026
This issue might be a duplicate of existing issues. Please check:
For keybind-related issues, please also check our pinned keybinds documentation: #4997
Mrqqeat commentedon May 15, 2026
All linked issues are closed, but the bug still exists in the latest version. This is a regression.
prepin commentedon Jun 23, 2026
it's
ctrl+aandctrl+ein default bindings insteadubunatic commentedon Jun 26, 2026
Home/End have been std. keys for decades to jump to start/end in input boxes.
Please consider adding these as (additional) defaults. Windows/Linux users' typing muscles will benefit.
The current C-a and C-e defaults are dual-key bindings that are harder to type and reach, also because left Ctrl requires pinky finger, which may often feels unnatural.
I vote ➕ for this, since home/end text navigation is ubiquitous.
taviso commentedon Jun 30, 2026
I was experimenting with opencode for the first time and hit this too, I think they get clobbered by
messages_firstandmessages_last.This seems to help in
~/.config/opencode/tui.jsongithub-actions commentedon Aug 30, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
kylebakerio commentedon Sep 26, 2026
this really is a pain. jumping to the top of the conversation is not really a common thing to need, there's already a secondary obscure keybinding added for that for users who do want it, and home/end to jump around within text is standard muscle memory for programmers everywhere. it makes opencode feel like a very unserious product that isn't built by devs, for devs, to not respect that convention used literally everywhere inputs are used.