[Feature]: Keep agent name first in sidebar rows for the monitoring state
- Dominant language
- TypeScript
- Stars
- 69.7k
- Forks
- 4.5k
- Avg merge
- 15h 28m
- Merged PRs (30d)
- 471
Description
### Problem or use case
Orca 1.4.192, macOS (Apple Silicon).
In the worktree card's agent list, rows for agents in the new *monitoring* state (yellow radio icon) render with the status label first:
- monitoring row: `Monitoring background tasks - `
- every other state: ` - `
At default sidebar width the 27-character status label truncates to "Monitoring backgroun…", so the agent name after the dash is pushed entirely out of view. With two or more agents monitoring at once (e.g. a coordinator and a log monitor), their rows become visually identical and can only be told apart by hovering each one for the tooltip.
The monitoring status is already conveyed by the yellow radio status icon on the same row (and by the hover tooltip), so the leading text label duplicates what the icon shows.
### Proposed solution
Keep name-first ordering for monitoring rows too: ` - Monitoring background tasks` — consistent with every other agent state. Alternatively, make the ordering configurable.
### Alternatives or additional context
- Current workaround: hover each row for the full tooltip, or widen the sidebar past the 27-character label.
- For reference, the ordering comes from the compact agent row in `WorktreeCard`: `leadingText = dotState === "monitoring" ? secondary : primary` (other states use `primary` = the agent/conversation name as the leading text).
Contributor guide
Research direction
Start at the compact agent row in WorktreeCard, where leadingText is selected from the monitoring state. Check the row rendering at the default sidebar width and make monitoring rows use the agent name first, matching other states. Done means monitoring rows show “ - Monitoring background tasks” and remain distinguishable without hovering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 88/100