FleetView: duplicated section headers after navigating into an agent and back

Status Fixed / completed
Maintainer reply ✓ Yes — bogini
Activity 3 comments · opened May 13, 2026 · closed May 14, 2026
💡 Likely answer: A maintainer (bogini, collaborator) responded on this thread — see the highlighted reply below.

Description

In the claude agents terminal tab (FleetView), navigating into an agent's detail view and then returning to the agent list leaves the section headers (Needs input, Completed, etc.) rendered twice and partially overlapping. The list rows render correctly, but the headers are stacked/duplicated until the terminal is forced to fully redraw.

Repro

  1. Open the claude agents tab with at least one agent in each of: Needs input, Working, Completed.
  2. Click into any agent to enter its detail view.
  3. Navigate back to the agent list.
  4. Observe duplicated Needs input and Completed section headers at the top of their respective sections.

Workaround

Resizing the terminal window forces a full redraw and clears the duplicates. Ctrl+L sometimes works too. This has to be done every time the user navigates back from an agent detail view, which is disruptive in normal multi-agent workflows.

Environment

  • OS: Windows 11 Home 10.0.26200
  • Terminal: Windows Terminal
  • Shell: PowerShell
  • Claude Code model: Opus 4.7

Screenshot

Available on request — local path on reporter's machine, can attach via web UI if helpful.

View original on GitHub ↗

3 Comments

github-actions[bot] · 5 months ago

Found 2 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/58555
  2. https://github.com/anthropics/claude-code/issues/58579

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

bogini collaborator · 5 months ago

Thanks for the report — confirmed and fixed. Same root cause as #58487: a Windows-specific rendering issue that affected local Windows Terminal / PowerShell users. Ships in v2.1.143.

github-actions[bot] · 3 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.