Repository navigation
TUI garbled/corrupted display after long output or extended conversation, while underlying model output remains correct #15388
Description
Description
After a long model output or an extended conversation session, the opencode TUI display becomes garbled / corrupted (花屏) — characters overlap, the layout breaks, or partial/stale content bleeds into the wrong regions of the terminal.
Importantly, the underlying model output is correct. If you restart opencode and use /sessions to view the session history, the model responses display normally, confirming the data itself was not corrupted — this is purely a rendering/display issue.
Steps to Reproduce
- Start opencode in a terminal.
- Trigger a task that produces a large/long model output (e.g., ask for a full file rewrite or a lengthy explanation), or have an extended multi-turn conversation with many tool calls.
- Observe the TUI — text/layout becomes garbled or overlapping.
- Exit opencode and restart it.
- Run
/sessionsand open the same session — the output renders correctly, confirming the data is intact.
Screenshot and/or Share Link
OpenCode Version
1.2.15
Operating System
wsl2 ubuntu 22.04
Terminal
cursor terminal
Activity
github-actions commentedon Feb 27, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is the same, please add a "+1" or additional context to the existing reports rather than opening a new one.
kommander commentedon Feb 27, 2026
The characters are completely broken, subcell, which is not something opentui can do, so it rather seems like a terminal/system issue with font rendering. What OS and terminal is this?
wufei-png commentedon Feb 28, 2026
Operating System
wsl2 ubuntu 22.04
Terminal
cursor terminal
I also think it's either WSL2 or the Cursor Terminal's fault. But actually have this bug.
kommander commentedon Feb 28, 2026
I'd file that with cursor or VSCode for windows, because that is an issue with font glyphs it seems. Unfortunately opentui has not influence on the underlying glyphs rendering.
github-actions commentedon Apr 30, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.