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

Missing current session indicator in highlighted state. #2655

New Issue
Closed
opened 2026-02-16 17:36:37 -05:00 by yindo · 10 comments
yindo commented 2026-02-16 17:36:37 -05:00
Owner
Copy Link
Copy Source

Originally created by @conradkoh on GitHub (Nov 7, 2025).

Description

There was a fix for https://github.com/sst/opencode/issues/3977 yesterday, for a commit made in https://github.com/sst/opencode/pull/3980.

There are minor issues with the indicator not showing when the row is highlighted. As a user, if the latest session is the active one, I can't tell that it is so without pressing the arrows.

The main issue stems from when the row is highlighted for selection

  1. The indicator is not showing (i.e. the text is not indented)
  2. Even if the indicator were showing, the color of the highlight is the same as the color of the indicator which would make it invisible.

Perhaps while highlighted it should an inverted color.

Image Image

OpenCode version

1.0.36

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

MacOS Tahoe 26.1

Terminal

iTerm2

Originally created by @conradkoh on GitHub (Nov 7, 2025). ### Description There was a fix for https://github.com/sst/opencode/issues/3977 yesterday, for a commit made in https://github.com/sst/opencode/pull/3980. There are minor issues with the indicator not showing when the row is highlighted. As a user, if the latest session is the active one, I can't tell that it is so without pressing the arrows. The main issue stems from when the row is highlighted for selection 1. The indicator is not showing (i.e. the text is not indented) 2. Even if the indicator were showing, the color of the highlight is the same as the color of the indicator which would make it invisible. Perhaps while highlighted it should an inverted color. <img width="548" height="198" alt="Image" src="https://github.com/user-attachments/assets/96ea9255-d80c-4bdb-92c2-c7e94c918216" /> <img width="539" height="252" alt="Image" src="https://github.com/user-attachments/assets/5753808a-6c56-417b-a44f-0fe9490178f1" /> ### OpenCode version 1.0.36 ### Steps to reproduce _No response_ ### Screenshot and/or share link _No response_ ### Operating System MacOS Tahoe 26.1 ### Terminal iTerm2
yindo added the bug label 2026-02-16 17:36:37 -05:00
yindo closed this issue 2026-02-16 17:36:37 -05:00
yindo commented 2026-02-16 17:36:38 -05:00
Author
Owner
Copy Link
Copy Source

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

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

  • #3977: Missing Current Session Indicator - This is the exact same issue that was already fixed in PR #3980, but issue #4024 reports that the indicator is not showing when the row is highlighted for selection

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

@github-actions[bot] commented on GitHub (Nov 7, 2025): This issue might be a duplicate of existing issues. Please check: - #3977: Missing Current Session Indicator - This is the exact same issue that was already fixed in PR #3980, but issue #4024 reports that the indicator is not showing when the row is highlighted for selection Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:36:38 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 7, 2025):

i left that on purpose guess u don’t like? haha

@rekram1-node commented on GitHub (Nov 7, 2025): i left that on purpose guess u don’t like? haha
yindo commented 2026-02-16 17:36:38 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 7, 2025):

/oc read the commits from the pr mentioned in the issue, adjust the dialog so that the current selection indicator is always present rather than only being present if the current item isnt the item being hovered over

@rekram1-node commented on GitHub (Nov 7, 2025): /oc read the commits from the pr mentioned in the issue, adjust the dialog so that the current selection indicator is always present rather than only being present if the current item isnt the item being hovered over
yindo commented 2026-02-16 17:36:38 -05:00
Author
Owner
Copy Link
Copy Source

@opencode-agent[bot] commented on GitHub (Nov 7, 2025):

Created PR #4025

New%20session%20-%202025-11-07T05%3A59%3A27.653Z
opencode session  |  github run

@opencode-agent[bot] commented on GitHub (Nov 7, 2025): Created PR #4025 <a href="https://opencode.ai/s/3xiFed0h"><img width="200" alt="New%20session%20-%202025-11-07T05%3A59%3A27.653Z" src="https://social-cards.sst.dev/opencode-share/TmV3IHNlc3Npb24gLSAyMDI1LTExLTA3VDA1OjU5OjI3LjY1M1o=.png?model=opencode/glm-4.6&version=1.0.39&id=3xiFed0h" /></a> [opencode session](https://opencode.ai/s/3xiFed0h)&nbsp;&nbsp;|&nbsp;&nbsp;[github run](/sst/opencode/actions/runs/19159681974)
yindo commented 2026-02-16 17:36:38 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 7, 2025):

ill double check it tmr but im p sure this is the change ur looking for

@rekram1-node commented on GitHub (Nov 7, 2025): ill double check it tmr but im p sure this is the change ur looking for
yindo commented 2026-02-16 17:36:38 -05:00
Author
Owner
Copy Link
Copy Source

@conradkoh commented on GitHub (Nov 7, 2025):

i left that on purpose guess u don’t like? haha

@rekram1-node HAHA oops! I actually don't mind it too much, but I guess my brain gets a little confused and I stall a little bit, because I'm not sure if the active session is outside of the scroll view or whether it is the first one. So I usually navigate away to double check it haha.

The way I'm using it right now is that in some repos (e.g. documentation) I might be working on several tasks in parallel. In these cases I actually need to jump back to old sessions and try to use them. I think this is not how most people are using it probably.

I feel that there are alternative "solutions" that indirectly solve the problem:

  1. automatically selecting the currently active session when the session picker appears
  2. using the last updated date as the session sort order rather than created date, so that the latest session used is always at the top of the list
  3. ability to pin long-lived sessions

Thanks for looking into this!

@conradkoh commented on GitHub (Nov 7, 2025): > i left that on purpose guess u don’t like? haha @rekram1-node HAHA oops! I actually don't mind it too much, but I guess my brain gets a little confused and I stall a little bit, because I'm not sure if the active session is outside of the scroll view or whether it is the first one. So I usually navigate away to double check it haha. The way I'm using it right now is that in some repos (e.g. documentation) I might be working on several tasks in parallel. In these cases I actually need to jump back to old sessions and try to use them. I think this is not how most people are using it probably. I feel that there are alternative "solutions" that indirectly solve the problem: 1. automatically selecting the currently active session when the session picker appears 2. using the last updated date as the session sort order rather than created date, so that the latest session used is always at the top of the list 3. ability to pin long-lived sessions Thanks for looking into this!
yindo commented 2026-02-16 17:36:38 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 7, 2025):

yeah ofc, ability to pin is prolly separate but the other 2 make sense ofc

@rekram1-node commented on GitHub (Nov 7, 2025): yeah ofc, ability to pin is prolly separate but the other 2 make sense ofc
yindo commented 2026-02-16 17:36:38 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 7, 2025):

the only thing with last updated is I think it’s currently and expensive lookup to sort my last updated ill have to see tho

@rekram1-node commented on GitHub (Nov 7, 2025): the only thing with last updated is I think it’s currently and expensive lookup to sort my last updated ill have to see tho
yindo commented 2026-02-16 17:36:38 -05:00
Author
Owner
Copy Link
Copy Source

@conradkoh commented on GitHub (Nov 7, 2025):

yeah ofc, ability to pin is prolly separate but the other 2 make sense ofc

oh I mean more like, that if the main sessions I am working on are always pinned, then I won't worry about the current session not being in view because they will always be at the top. which means that I won't worry about the indicator getting pushed down outside of the screen. but perhaps that's a bit of a stretch too. I think I was trying to say that the UX is quite contextual to what the user is doing, and in my use case it is particularly geared towards using multiple long recurrent sessions.

the only thing with last updated is I think it’s currently and expensive lookup to sort my last updated ill have to see tho

yeah I can imagine that the way the data is organized plays quite a big role in this. I do think that sorting by last updated (if you had to choose) would make more sense as the primarily field to sort rows by though. assuming that at some point you would set a limit x to the number of sessions to store in history, it would be very unnatural if the xth record was dropped even though the user just accessed it.

@conradkoh commented on GitHub (Nov 7, 2025): > yeah ofc, ability to pin is prolly separate but the other 2 make sense ofc oh I mean more like, that if the main sessions I am working on are always pinned, then I won't worry about the current session not being in view because they will always be at the top. which means that I won't worry about the indicator getting pushed down outside of the screen. but perhaps that's a bit of a stretch too. I think I was trying to say that the UX is quite contextual to what the user is doing, and in my use case it is particularly geared towards using multiple long recurrent sessions. > the only thing with last updated is I think it’s currently and expensive lookup to sort my last updated ill have to see tho yeah I can imagine that the way the data is organized plays quite a big role in this. I do think that sorting by last updated (if you had to choose) would make more sense as the primarily field to sort rows by though. assuming that at some point you would set a limit `x` to the number of sessions to store in history, it would be very unnatural if the `x`th record was dropped even though the user just accessed it.
yindo commented 2026-02-16 17:36:38 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 7, 2025):

Ah okay yeah definitely agree on both of those

@rekram1-node commented on GitHub (Nov 7, 2025): Ah okay yeah definitely agree on both of those
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 bug
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#2655
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?