anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 18:25:32 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

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

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

Originally created by @ariane-emory on GitHub (Nov 27, 2025).

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.

Originally created by @ariane-emory on GitHub (Nov 27, 2025). ### 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 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`.
yindo added the discussion label 2026-02-16 17:38:57 -05:00
yindo closed this issue 2026-02-16 17:38:57 -05:00
yindo commented 2026-02-16 17:38:57 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Nov 27, 2025):

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

  • #3125: Jump to current output point

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

@github-actions[bot] commented on GitHub (Nov 27, 2025): This issue might be a duplicate of existing issues. Please check: - #3125: Jump to current output point Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:38:57 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 2, 2025):

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

@rekram1-node commented on GitHub (Dec 2, 2025): Have you used /timeline @ariane-emory it kinda servers teh same purpose
yindo commented 2026-02-16 17:38:57 -05:00
Author
Owner
Copy Link
Copy Source

@ariane-emory commented on GitHub (Dec 2, 2025):

@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.

@ariane-emory commented on GitHub (Dec 2, 2025): @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 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
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#3169
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?