Skip to content

[FEATURE]: add a command to scroll back to the user's last message #4847

Closed

Description

@ariane-emory

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

Often I'll send a message to the model and switch windows or go AFK while the model proceeds to work and produce many pages of output. When I return, I'll want to review that output to see what it did.

Currently, I'll have to manually scroll back and forth until I find the last message I sent so that I can read on from there.

It would improve the ergonomics and UX if there were a command that would scroll the session back to the last message sent by the user. We could call it last_user_message or something like that?

I don't really care what key it's bound do, I can bind a key for it myself in my opencode.jsonc.

Activity

  1. added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Nov 28, 2025
  2. github-actions commented on Nov 28, 2025

    @github-actions
    Contributor

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

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

  3. rekram1-node commented on Dec 2, 2025

    @rekram1-node
    Collaborator

    Have you used /timeline @ariane-emory it kinda servers teh same purpose

  4. ariane-emory commented on Dec 2, 2025

    @ariane-emory
    ContributorAuthor

    @rekram1-node I have, and you are correct that it can serve a somewhat similar purpose, but it is somewhat less ergonomic:

    • It requires at least two more keystrokes (<up> to wrap around from the top of the list to the bottom, followed by <enter> to select the entry in the list) to get to my last message.
    • since messages from plugins are also in the timeline, <up><enter> might not get you back to the last message you types: additional keystrokes - and, more importantly, additional time thinking to distinguish plugin messages from actual user messages - might be required in these cases.

    I wanted a more ergonomic solution, that would allow me to mindlessly whack one single key to get to the last message that I had actually typed myself, without being distracted from whatever train of though I'd been previously thinking about on expending the mental effort the distinguis plugin-originated messages from actual user-typed messages and navigating to the correct entry: just whack one key and done, without any focus-breaking faffing about selecting from menu items.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    discussionUsed for feature requests, proposals, ideas, etc. Open discussion

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions