Agents view: navigating into an agent and back (←) leaves stale/garbled frame until terminal resize

Status Fixed / completed
Reported on v2.1.165
Maintainer reply ✓ Yes — bcherny
Activity 4 comments · opened Jun 5, 2026 · closed Aug 19, 2026
💡 Likely answer: A maintainer (bcherny, collaborator) responded on this thread — see the highlighted reply below.

Summary

In the multi-agent task list ("agents") view, opening an agent's detail and then returning to the list does only a partial redraw. The previous detail content overlaps the task list, header, and logo art. The TUI does not perform a full repaint on back-navigation, so the list view stays corrupted.

Environment

  • Version: 2.1.165
  • OS: Windows Terminal + WSL2 (Ubuntu), 6.6.x-microsoft-standard-WSL2

Steps to reproduce

  1. Have at least 2 background agents/tasks so the agents list view shows entries.
  2. From the agents list, enter an agent's detail (→ / enter).
  3. Navigate back to the list (←).
  4. The list view is rendered garbled — stale detail-frame content overlaps the task rows, header, and logo.

Workaround

  • Any terminal resize triggers SIGWINCH → full repaint → fixes it.
  • pkill -WINCH -f claude (sends SIGWINCH without moving the window) also fixes it.
  • Ctrl+L does not fix it.

Expected

A full repaint on back-navigation, leaving no stale frame from the agent detail view.

View original on GitHub ↗

3 Comments

artur-st · 3 months ago

@bogini, any progress here? This issue is very unfortunate for all Windows users.

gknedo · 3 months ago

Happening here, seems to start if I resize the window. After the first resize, whenever I minimize and maximize the claude window, this bug appears

bcherny collaborator · 1 month ago

Fixed in 2.1.169 — changelog: "Fixed agents view leaving a stale/garbled frame after navigating back from an agent on WSL in Windows Terminal" (https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md). Closing — reply to reopen if it still happens on the latest version.

🤖 Generated with Claude Code

Showing cached comments. Read the full discussion on GitHub ↗