FleetView row loses session title after detaching back from an attached session (macOS)

Status Closed — not planned
Reported on v2.1.205
Maintainer reply None cached
Activity 4 comments · opened Jul 9, 2026 · closed Aug 23, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet (related but distinct: #58555)
  • [x] This is a single bug report
  • [x] I am using the latest version of Claude Code

What's Wrong?

In agent view (claude agents), after attaching to a session with → and then detaching back to the dashboard with ← (on an empty prompt), the row's session title in the Working section becomes blank. The underlying session name isn't actually lost — running /status inside the session still shows the correct Session name, and re-entering the same name via /rename restores the visible title in agent view.

What Should Happen?

The session title should remain visible in agent view after detaching, without needing to manually re-run /rename.

Steps to Reproduce

  1. Run claude agents to open agent view.
  2. Attach to any session row with → (or Enter).
  3. Detach back to the dashboard with ← on an empty prompt.
  4. The row's title is now blank in the Working/session list.
  5. Workaround: run /status inside the session to see the actual Session name, then run /rename <same name> — the title reappears in agent view.

Error Messages/Logs

(none — display-only issue, no error output)

Claude Model

Sonnet 5 (claude-sonnet-5)

Is this a regression?

Unknown — not tested on earlier versions.

Last Working Version

No response

Environment

  • Claude Code version: 2.1.205
  • OS: macOS (Darwin 23.6.0)

Related

Possibly related to #58555 ("FleetView dashboard layout broken after returning from session", Windows-specific stale-terminal-width bug, fixed in v2.1.143) but that issue was confirmed Windows-only and this is being seen on macOS on a version newer than the fix, so it may be a separate root cause. Filing separately rather than reopening #58555.

View original on GitHub ↗

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