anomalyco / anomalyco/opencode
The shortcuts for jumping to next or previous message not working well wiht long response/message
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
I'm using OpenCode CLI v2.0.8. I mapped session.message.next to ctrl+down and session.message.previous to ctrl+up. I found if I have multiple responses/messages and some of them are relatively long, then the jumping to next or previous commands/shortcuts don't work very well, they'll jump to somewhere in the middle of the long response/message, not precisely to the next or previous one!
With OpenCode CLI v1.18.31, these commands/shortcuts work better for long responses/messages, but still if the responses/messages for very long, then they have same problem.
But in both v1 & v2, if I use <leader>g (ctrl+x,g) to trigger the Timeline , popup to let me navigate through and jump between them precisely. So don't think there should be any technical difficulties for session.message.next & session.message.previous to achieve the same.
Plugins
No response
OpenCode version
v2.0.8
Steps to reproduce
No response
Screenshot and/or share link
No response
Operating System
Windows 11
Terminal
Windows Terminal
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the session.message.next and session.message.previous shortcut handling in the OpenCode CLI, then compare their behavior with the Timeline navigation triggered by g. Reproduce on Windows Terminal with multiple messages, including very long responses, and confirm that each shortcut lands on the next or previous message rather than inside its content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100