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

[FEATURE]: Add ability to (un)mark points in the thread, to use as "bookmarks" #6684

New Issue
Open
opened 2026-02-16 18:04:57 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:04:57 -05:00
Owner
Copy Link
Copy Source

Originally created by @alexaandru on GitHub (Jan 18, 2026).

Originally assigned to: @rekram1-node on GitHub.

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

The idea is plainly stolen from vim: add ability to set/unset marks in the thread. Related to it, would be the (optional?) display of marks in the thread (a "hr" ------- or something).

The usecase is: keeping track with what was reviewed so far in the thread, mark it, then do something else, then when you come back to opencode, either scroll back up to that mark or, even better, be able to jump straight to the mark (optionally remove it), review the new stuff, repeat.

The smarter the LLMs become -> the more they can work on their own -> the more important is to have some good tools to manage navigation of the consequently longer threads. I think marks+jumps would be an excellent addition.

Optionally, ability to annotate the marks with a message would also be useful.
Optionally 2, having the marks indicated in the scrollbar itself, would also be nice :-)

Originally created by @alexaandru on GitHub (Jan 18, 2026). Originally assigned to: @rekram1-node on GitHub. ### 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 The idea is plainly stolen from vim: add ability to set/unset marks in the thread. Related to it, would be the (optional?) display of marks in the thread (a "hr" ------- or something). The usecase is: keeping track with what was reviewed so far in the thread, mark it, then do something else, then when you come back to opencode, either scroll back up to that mark or, even better, be able to jump straight to the mark (optionally remove it), review the new stuff, repeat. The smarter the LLMs become -> the more they can work on their own -> the more important is to have some good tools to manage navigation of the consequently longer threads. I think marks+jumps would be an excellent addition. Optionally, ability to annotate the marks with a message would also be useful. Optionally 2, having the marks indicated in the scrollbar itself, would also be nice :-)
yindo added the opentuidiscussion labels 2026-02-16 18:04:57 -05:00
yindo commented 2026-02-16 18:04:57 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 18, 2026):

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

  • #5077: [FEATURE]: Add keybind to navigate between user messages
  • #5029: [FEATURE]: Add keybinds to scroll to prev/next user message
  • #3337: Feature Request: Navigation Shortcut to Jump Between User Messages
  • #4092: [FEATURE]: better navigation of output, alternative vim mode and non-blocking agent permission requests
  • #2755: feat: Copy Mode for OpenCode (discusses vim-like navigation and marks in scrollbar)

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

@github-actions[bot] commented on GitHub (Jan 18, 2026): This issue might be a duplicate of existing issues. Please check: - #5077: [FEATURE]: Add keybind to navigate between user messages - #5029: [FEATURE]: Add keybinds to scroll to prev/next user message - #3337: Feature Request: Navigation Shortcut to Jump Between User Messages - #4092: [FEATURE]: better navigation of output, alternative vim mode and non-blocking agent permission requests - #2755: feat: Copy Mode for OpenCode (discusses vim-like navigation and marks in scrollbar) Feel free to ignore if none of these address your specific case.
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 opentui
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#6684
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?