Repository navigation
Closed as duplicate
Closed as duplicate
Copy link
Labels
Description
Consolidated tracker for stale terminal-rendering issues closed in the July 2026 stale-issue sweep (no activity since 2026-06-01).
Each issue below was closed as a duplicate of this tracker. If any of them still reproduces (or is still wanted) on a current build, comment here or on the original issue and we'll reopen it.
- [bug] CJK glyph corruption in terminal output (1.9.6) #4639 — [bug] CJK glyph corruption in terminal output (1.9.6)
- terminal becomes unreadable #4183 — terminal becomes unreadable
- [bug] Terminal intermittently renders English text as RTL-looking gibberish #4010 — [bug] Terminal intermittently renders English text as RTL-looking gibberish
- Terminal renders garbled characters (WebGL texture atlas corruption) #3794 — Terminal renders garbled characters (WebGL texture atlas corruption)
- [bug] Claude code rendering issue in superset terminal #3668 — [bug] Claude code rendering issue in superset terminal
- [bug] Intermittent garbled text rendering with multiple Claude Code tabs and Chinese content #3572 — [bug] Intermittent garbled text rendering with multiple Claude Code tabs and Chinese content
- [Bug] Latin/ASCII characters render as corrupted glyphs when mixed with Chinese text #3570 — [Bug] Latin/ASCII characters render as corrupted glyphs when mixed with Chinese text
- [bug] Terminal Output Corruption (Garbled CJK Characters) and Layout Glitches during Heavy Usage #3527 — [bug] Terminal Output Corruption (Garbled CJK Characters) and Layout Glitches during Heavy Usage
- [bug] macOS terminal rendering can corrupt and ghost into chat until fullscreen toggle #3504 — [bug] macOS terminal rendering can corrupt and ghost into chat until fullscreen toggle
- Opening Coding Assistant doesn't fill the width of the screen #3482 — Opening Coding Assistant doesn't fill the width of the screen
- [bug] opencode doesn't fully fit the terminal #3468 — [bug] opencode doesn't fully fit the terminal
- Agentic sessions are using half of availlable space. #3413 — Agentic sessions are using half of availlable space.
- [bug] Sometimes the displayed Chinese characters are garbled. #3406 — [bug] Sometimes the displayed Chinese characters are garbled.
- [bug] Jumbled up output with Claude sessions #3377 — [bug] Jumbled up output with Claude sessions
- [bug] Terminal ghosting and accumulating black regions after workspace switches #3351 — [bug] Terminal ghosting and accumulating black regions after workspace switches
- [bug] Terminal can still repaint into a stale visual state after focus/workspace restore #3321 — [bug] Terminal can still repaint into a stale visual state after focus/workspace restore
- OpenCode terminal screen glitch and temporary recovery issue when switching between Superset multi-workspaces #3313 — OpenCode terminal screen glitch and temporary recovery issue when switching between Superset multi-workspaces
- [bug] Codex terminal state corrupts on pane reattach after tab/workspace switch #3309 — [bug] Codex terminal state corrupts on pane reattach after tab/workspace switch
- [bug] new terminal starts in half width #3281 — [bug] new terminal starts in half width
- [bug] when focusing back on terminal, content gets corrupted #3208 — [bug] when focusing back on terminal, content gets corrupted
- Prompt lines duplicate/stack up when resizing window via keyboard shortcut (Cmd+/-) #3179 — Prompt lines duplicate/stack up when resizing window via keyboard shortcut (Cmd+/-)
- [bug] TUI rendering broken: content duplication, text cutoff, and wasted horizontal space #3080 — [bug] TUI rendering broken: content duplication, text cutoff, and wasted horizontal space
- [bug] fonts turning to garbage #2514 — [bug] fonts turning to garbage
- [bug] Codex output disappears after switching away from Superset and back #2507 — [bug] Codex output disappears after switching away from Superset and back
- [bug] Underline decoration misaligned with CJK/mixed-width text in terminal #2231 — [bug] Underline decoration misaligned with CJK/mixed-width text in terminal
- [bug] When I switch away from a terminal tab and come back, the input bar appears twice. Additionally, the terminal view is auto-scrolled to the bottom, leaving a large blank space. #1830 — [bug] When I switch away from a terminal tab and come back, the input bar appears twice. Additionally, the terminal view is auto-scrolled to the bottom, leaving a large blank space.
Activity
github-actions commentedon Jul 11, 2026
Automated triage note
This is a consolidated tracker, not a single reproducible defect — it bundles 26 previously-closed
terminal-renderingissues from the July 2026 stale sweep. I walked the desktop terminal rendering + transport subsystem (apps/desktop/src/renderer/lib/terminal/*,.../TabsContent/Terminal/*,apps/desktop/src/main/lib/terminal*) to check whether the cluster shares a single root cause that could be pinned with abun:testreproduction. It doesn't, and a headless unit test can't exercise any of these — they only manifest against a real Electron renderer with WebGL/Canvas, a running font loader, and live flex layout:bun test.FitAddon.fit()measuring against an unresolved flex layout or racing a font load; needs real layout +ResizeObserver.The pure, headless-testable helpers along this path (
write-coalescer, theterminal-ws-transportframing,truncateUtf8ToLastBytes,convertLinkRangeToBuffer) are already byte-/boundary-safe and carry regression tests, and the subsystem already ships targeted mitigations for several of these exact reports — e.g.terminal-runtime.tsactivates Unicode-11 widths before buffer replay citing #3572, andfont-settle.ts, the write-coalescer, and the clipboard/appearance guards address the same families. So the tractable logic layer is already covered; what remains is genuinely renderer/GPU behavior.Recommendation: these need an Electron integration/E2E harness (drive the renderer over CDP, per
apps/desktop/AGENTS.md) or manual verification on a current build, reproduced per individual issue — not one shared unit test. Per this tracker's own note, anyone still hitting a specific glitch on a current build should comment with the build version and repro steps so the individual issue can be reopened and triaged with the right harness.No PR opened — there is no single-root-cause defect to fix or to reproduce headlessly.