UI breaking with no pattern #52939

Activity

1. github-actions

   assigned

   kommander

   on Oct 3, 2026
2. github-actions commented on Oct 3, 2026

   

   github-actionsBot

   on Oct 3, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • #51945: Similar v2 TUI rendering failure where parts of the UI become invisible; it occurs after terminal resize or screen saver activation.
   • #5283: Reports random graphical glitches that cause the TUI to break down.
   • #3935: Reports disappearing TUI content that temporarily returns after changing the theme to force a redraw.
3. EduLGFon commented on Oct 3, 2026

   

   EduLGFon

   on Oct 3, 2026

   Author

   More actions

   It do not seems to be any of those issues.
   My current opencode settings:
   appearance
   Theme: opencode
   color mode: system
   animations: on

   session
   sidebar: hide
   scrollbar: on
   thinking: show
   markdown: rendered
   tool grouping: auto
   verbosity: high
   transcript images: on
   TPS: on
   new session location: launch directory
   permissions: auto accept

   tabs
   mode: on
   scope: current directory
   layout: horizontal
   indicators: status icons

   diffs
   layout: auto
   wrapping: word
   file tree: on
   single patch: off

   input
   scroll speed: 3.00
   acceleration: off
   mouse: on
   editor context: on
   large pastes: full
   image previews: off
   leader timeout: 2000 ms

   alerts
   notifications: on
   sounds: off
   volume: 100%

   terminal
   window title: on
   copy behavior: select

   debug
   developer tools: off
4. opencodejr commented on Oct 27, 2026

   

   opencodejrBot

   on Oct 27, 2026

   Contributor

   More actions

   Thanks for the report and the screenshot, @EduLGFon. They show what's going on. The lines drawn over the UI (ALSA lib confmisc.c:855:(parse_card) cannot find card '0', Unknown PCM dmix, …) are errors from the Linux audio library. On a machine with no sound card, the TUI's audio backend makes ALSA print these errors straight to the terminal when a notification sound plays, for example when a turn finishes. The TUI then only partly repaints, which is why changing the theme (a full redraw) fixes it for a while.

   I think this is a duplicate of #41763. Possible duplicates and related issues, ordered from most to least likely:

   • tui: ALSA errors flood and corrupt the terminal during interaction #41763: ALSA errors flood and corrupt the TUI on Linux hosts with no sound card. This is the open tracking issue.
   • TUI: ALSA stderr errors from the session-complete notification sound corrupt the display on machines without audio devices #54130: same symptom on a headless Ubuntu 24.04 machine, triggered when a response finishes (closed as a duplicate of tui: ALSA errors flood and corrupt the terminal during interaction #41763).
   • tui: garbled display / raw ANSI on WSL when native audio backend writes ALSA errors to stderr #52793: same ALSA-over-TUI corruption on WSL with v2.0.22 (closed as a duplicate of tui: ALSA errors flood and corrupt the terminal during interaction #41763).
   • tui: attention sound corrupts the terminal when no audio device is available #55302 / TUI sounds print ALSA lib errors into terminal on audio-less devices (Termux/Android) #51841: same cause, reported on WSL2 and Termux.
   • fix(tui): keep native and child stderr off the rendered screen #59128: open PR that stops native stderr from being drawn over the TUI.

   Until that's fixed, a workaround that may help is turning off attention sounds in your tui.json:

   {
     "$schema": "https://opencode.ai/tui.json",
     "attention": { "sound": false }
   }

   Please subscribe to or 👍 #41763 to follow progress. The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different.
5. opencodejr

   added

   pending close

   triaging

   on Oct 27, 2026
6. opencodejr

   closed this as duplicateon Oct 28, 2026
7. opencodejr commented on Oct 28, 2026

   

   opencodejrBot

   on Oct 28, 2026

   Contributor

   More actions

   Closing this as a duplicate of #41763, since there's been no reply in the past day. The lines drawn over the UI in your screenshot (ALSA lib ... cannot find card '0') come from the TUI's audio backend. On Linux machines with no sound card, ALSA writes its errors straight to the terminal when a notification sound plays, and the TUI only partly repaints afterwards. That is the problem tracked in #41763, and open PR #59128 addresses it.

   Until it's fixed, setting "attention": { "sound": false } in your tui.json may help. Please subscribe to or 👍 #41763 to follow progress. If your problem turns out to be different, reply here and we'll take another look.