Skip to content

[Bug] Home/End keys in input box scroll message list instead of moving cursor #27661

Closed as not planned

Description

@Mrqqeat

Description

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

  1. Focus on the message input box.
  2. Type a long sentence.
  3. Press the Home key to try and return to the start of the sentence.
  4. 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

Activity

  1. github-actions commented on May 15, 2026

    @github-actions
    Contributor

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

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

  2. Mrqqeat commented on May 15, 2026

    @Mrqqeat
    Author

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

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

    All linked issues are closed, but the bug still exists in the latest version. This is a regression.

  3. prepin commented on Jun 23, 2026

    @prepin

    it's ctrl+a and ctrl+e in default bindings instead

  4. ubunatic commented on Jun 26, 2026

    @ubunatic

    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.

  5. taviso commented on Jun 30, 2026

    @taviso

    I was experimenting with opencode for the first time and hit this too, I think they get clobbered by messages_first and messages_last.

    This seems to help in ~/.config/opencode/tui.json

    {
      "$schema": "https://opencode.ai/tui.json",
      "keybinds": {
        "messages_first": "none",
        "messages_last": "none"
      }
    }
    
  6. github-actions commented on Aug 30, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

  7. kylebakerio commented on Sep 26, 2026

    @kylebakerio

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions