Skip to content

fix(sidebar): show background status in flat thread rows - #438

Merged
Tryanks merged 1 commit into
mainfrom
fix/flat-thread-background-status
Sep 15, 2026
Merged

Tryanks merged 1 commit into
mainfrom
fix/flat-thread-background-status

Conversation

@Tryanks

@Tryanks Tryanks commented Sep 15, 2026

Copy link
Copy Markdown
Owner

Problem

A thread whose turn had finished but still owned provider background tasks (e.g. a Claude Monitor watching CI) showed Working in the flat thread list. The grouped view already showed Background via thread_status_badge; the flat root row rendered its own second-line status text and only checked working.

Runtime and the Claude adapter are correct (verified by replaying a real Monitor trace: result publishes BackgroundTasksChanged{1} then TurnCompleted). The fork was UI-only.

Fix

  • Extract thread_status_label (approval → input → background → working) and use it for the badge, the flat second-line text, and the flat status dot.
  • Align flat rows with the grouped row: flat child rows show the worktree glyph; renaming hides dots and the timestamp/archive slot.
  • Document the three thread-row shapes and their deliberate differences in docs/DESIGN.md.

Net -4 lines. cargo test -p tcode-ui --lib sidebar passes; clippy clean.

The flat thread list rendered its own status text and dot and only checked
`working`, so a thread whose turn had finished but still owned provider
background tasks (e.g. a Claude Monitor) showed "Working" instead of
"Background". Extract thread_status_label and use it for the badge, the
flat second-line text and the flat status dot.

Also align the flat shapes with the grouped row: flat child rows show the
worktree glyph, and renaming hides dots and the timestamp slot. Document
the three row shapes and their deliberate differences in DESIGN.md.
@Tryanks
Tryanks merged commit eb45211 into main Sep 15, 2026
6 checks passed
@Tryanks
Tryanks deleted the fix/flat-thread-background-status branch September 15, 2026 21:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant