TUI rendering: /agents view lines stack/overlap on Windows Terminal (2.1.140)

Resolved 💬 6 comments Opened May 13, 2026 by MankhongGarden Closed May 14, 2026

Environment

  • Claude Code: 2.1.140
  • OS: Windows 11 Home (build 26200.7019)
  • Terminal: Windows Terminal 1.24.10921.0 (set as default via HKCU\Console\%%Startup delegation GUIDs)
  • Shell: PowerShell 7.6.1 (MSIX, user-scope)
  • Node: 22.22.2 / npm 10.9.7

What happens

Opening the /agents view (added in 2.1.139) causes lines in the TUI to stack/overlap on top of each other. Selected items, headers, and list rows render on top of one another instead of in separate rows. The result is unreadable — multiple lines collapse into one visual line.

Issue persists after migrating the default terminal from legacy conhost to Windows Terminal (verified via registry).

Reproduction

  1. Open Windows Terminal (default profile: PowerShell 7)
  2. Run claude in any directory
  3. Type /agents
  4. Observe: list rows overlap; arrow-key navigation shifts overlap location but doesn't clear it

Expected

Each agent / menu row renders on its own line, like other TUI views (e.g. /mcp, /permissions).

Workarounds tried

  • Ctrl+L — no effect (corruption sits in the Ink virtual buffer, not the terminal scrollback)
  • Resizing the WT window — forces a full repaint and partially clears the overlap, but it returns on next interaction
  • Switching default terminal conhost → WT — no change

Related issues

  • #52410 — permission prompt render-loop collapsing line height on WT (closest symptom match)
  • #19637 — long-standing Windows TUI overlap/garble since 2.1.3
  • #20405 — "Rendering in Windows Terminal is broken" (closed/stale)
  • #16578 — status lines stacking instead of updating in place

None of the above mention the new /agents view specifically, so filing this to put it on the radar — /agents shipped 2 days ago (2.1.139) and the symptom is very visible there.

Suggested labels

area:tui · platform:windows · area:agents

View original on GitHub ↗

This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗