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

message history randomly flickers/disappears #2587

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

Originally created by @DanielFGray on GitHub (Nov 4, 2025).

Originally assigned to: @kommander on GitHub.

Description

seems to be a rendering issue since opentui rewrite where occasionally messages become invisible, scrolling up and down doesn't reveal them, and resizing doesnt properly redraw them

OpenCode version

v1.0.25

Steps to reproduce

it is hard to directly replicate, but seems to happen in nearly every long-running session

Screenshot and/or share link

No response

Operating System

arch linux

Terminal

lxterminal

Originally created by @DanielFGray on GitHub (Nov 4, 2025). Originally assigned to: @kommander on GitHub. ### Description seems to be a rendering issue since opentui rewrite where occasionally messages become invisible, scrolling up and down doesn't reveal them, and resizing doesnt properly redraw them ### OpenCode version v1.0.25 ### Steps to reproduce it is hard to directly replicate, but seems to happen in nearly every long-running session ### Screenshot and/or share link _No response_ ### Operating System arch linux ### Terminal lxterminal
yindo added the opentuibug labels 2026-02-16 17:36:20 -05:00
yindo closed this issue 2026-02-16 17:36:20 -05:00
yindo commented 2026-02-16 17:36:20 -05:00
Author
Owner
Copy Link
Copy Source

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

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

  • #3719: [navigating away from an active session causes it to flicker/be blank when returning to it] - Very similar flickering/blank session behavior
  • #3669: [Unable to Load Old Sessions] - Session history flashing and disappearing issue
  • #3697: [Missing main view text when resizing] - Text disappearing after window resize events
  • #3776: [Screen becomes completely blank] - Similar blank screen rendering issue

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

@github-actions[bot] commented on GitHub (Nov 4, 2025): This issue might be a duplicate of existing issues. Please check: - #3719: [navigating away from an active session causes it to flicker/be blank when returning to it] - Very similar flickering/blank session behavior - #3669: [Unable to Load Old Sessions] - Session history flashing and disappearing issue - #3697: [Missing main view text when resizing] - Text disappearing after window resize events - #3776: [Screen becomes completely blank] - Similar blank screen rendering issue Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:36:21 -05:00
Author
Owner
Copy Link
Copy Source

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

I think this is gonna be fixed in 1.0.21

@rekram1-node commented on GitHub (Nov 4, 2025): I think this is gonna be fixed in 1.0.21
yindo commented 2026-02-16 17:36:21 -05:00
Author
Owner
Copy Link
Copy Source

@kamilchm commented on GitHub (Nov 4, 2025):

Still happens to me on 1.0.23. :(
I found a workaround: Ctrl+P then Jump to message, or just Ctrl+X G.

@kamilchm commented on GitHub (Nov 4, 2025): Still happens to me on 1.0.23. :( I found a workaround: `Ctrl+P` then Jump to message, or just `Ctrl+X G`.
yindo commented 2026-02-16 17:36:21 -05:00
Author
Owner
Copy Link
Copy Source

@JonathanRiche commented on GitHub (Nov 5, 2025):

This still happens on 1.0.25 as well

@JonathanRiche commented on GitHub (Nov 5, 2025): This still happens on 1.0.25 as well
yindo commented 2026-02-16 17:36:21 -05:00
Author
Owner
Copy Link
Copy Source

@Rabeez commented on GitHub (Nov 5, 2025):

Partial 'hacky' fix to get back the messages is to trigger the "jump to message" action since it forces render

@Rabeez commented on GitHub (Nov 5, 2025): Partial 'hacky' fix to get back the messages is to trigger the "jump to message" action since it forces render
yindo commented 2026-02-16 17:36:21 -05:00
Author
Owner
Copy Link
Copy Source

@JonathanRiche commented on GitHub (Nov 5, 2025):

Partial 'hacky' fix to get back the messages is to trigger the "jump to message" action since it forces render

Yeh it's the only way i can use it right now lol

@JonathanRiche commented on GitHub (Nov 5, 2025): > Partial 'hacky' fix to get back the messages is to trigger the "jump to message" action since it forces render Yeh it's the only way i can use it right now lol
yindo commented 2026-02-16 17:36:21 -05:00
Author
Owner
Copy Link
Copy Source

@d33tah commented on GitHub (Nov 6, 2025):

How do you guys use the workaround without pressing esc, reverting code or forking? I want to keep the actions going, not terminate them.

@d33tah commented on GitHub (Nov 6, 2025): How do you guys use the workaround without pressing esc, reverting code or forking? I want to keep the actions going, not terminate them.
yindo commented 2026-02-16 17:36:21 -05:00
Author
Owner
Copy Link
Copy Source

@kamilchm commented on GitHub (Nov 6, 2025):

I actually switched to selecting /theme.

@kamilchm commented on GitHub (Nov 6, 2025): I actually switched to selecting `/theme`.
yindo commented 2026-02-16 17:36:21 -05:00
Author
Owner
Copy Link
Copy Source

@kommander commented on GitHub (Nov 6, 2025):

Is this still happening on the latest version 1.0.35?

@kommander commented on GitHub (Nov 6, 2025): Is this still happening on the latest version 1.0.35?
yindo commented 2026-02-16 17:36:21 -05:00
Author
Owner
Copy Link
Copy Source

@aaronmcadam commented on GitHub (Nov 6, 2025):

Is this still happening on the latest version 1.0.35?

Yes, I am still seeing bad performance, rendering problems, and bun crashes for sessions with a long message history with version 1.0.35.

@aaronmcadam commented on GitHub (Nov 6, 2025): > Is this still happening on the latest version 1.0.35? Yes, I am still seeing bad performance, rendering problems, and bun crashes for sessions with a long message history with version 1.0.35.
yindo commented 2026-02-16 17:36:21 -05:00
Author
Owner
Copy Link
Copy Source

@kommander commented on GitHub (Nov 6, 2025):

Could you share one such session that causes the issues? Are you also on linux?

@kommander commented on GitHub (Nov 6, 2025): Could you share one such session that causes the issues? Are you also on linux?
yindo commented 2026-02-16 17:36:21 -05:00
Author
Owner
Copy Link
Copy Source

@d33tah commented on GitHub (Nov 6, 2025):

@kommander what do I use to share one with you?

@d33tah commented on GitHub (Nov 6, 2025): @kommander what do I use to share one with you?
yindo commented 2026-02-16 17:36:21 -05:00
Author
Owner
Copy Link
Copy Source

@d33tah commented on GitHub (Nov 6, 2025):

Also, wild guess: could it be a bug in the progress bar / scrolling implementation? Something that adds a lot of blank space and the actual log is above?

@d33tah commented on GitHub (Nov 6, 2025): Also, wild guess: could it be a bug in the progress bar / scrolling implementation? Something that adds a lot of blank space and the actual log is above?
yindo commented 2026-02-16 17:36:21 -05:00
Author
Owner
Copy Link
Copy Source

@kommander commented on GitHub (Nov 6, 2025):

You can use /share and give the URL, if you don't want to have it public DM me on discord or twitter

@kommander commented on GitHub (Nov 6, 2025): You can use /share and give the URL, if you don't want to have it public DM me on discord or twitter
yindo commented 2026-02-16 17:36:21 -05:00
Author
Owner
Copy Link
Copy Source

@kommander commented on GitHub (Nov 6, 2025):

The problem is that the scrollbox has culling, but the culling is calculated before the children are updated by the layout. I thought I mitigated that, going to fix that properly tonight.

@kommander commented on GitHub (Nov 6, 2025): The problem is that the scrollbox has culling, but the culling is calculated before the children are updated by the layout. I thought I mitigated that, going to fix that properly tonight.
yindo commented 2026-02-16 17:36:21 -05:00
Author
Owner
Copy Link
Copy Source

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

Should be better in the upcoming version.

@kommander commented on GitHub (Nov 7, 2025): Should be better in the upcoming version.
yindo commented 2026-02-16 17:36:21 -05:00
Author
Owner
Copy Link
Copy Source

@DanielFGray commented on GitHub (Nov 11, 2025):

I haven't noticed this in a while, even on [some really] long sessions, so I'm gonna close it

@DanielFGray commented on GitHub (Nov 11, 2025): I haven't noticed this in a while, even on [some really] long sessions, so I'm gonna close it
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 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#2587
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?