[Bug]: Limits bar labels pooled accounts by number, so accounts cannot be told apart
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 23k
- Forks
- 5.9k
- Avg merge
- 11h 14m
- Merged PRs (30d)
- 357
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/web
Steps to reproduce
- Have two or more accounts or instances of one provider (for example four Claude accounts, or Codex instances across environments).
- Open Usage → Limits.
- Look at a pooled window (for example Claude → Session) at a width where the legend is shown.
Expected behavior
Each account is identifiable without opening its popover. The bar and its legend row show the account's own mark — the provider glyph with its accent initials badge, or the two-letter chip — the same mark the Limits popover, the model picker and thread rows already draw.
Actual behavior
The bar and every legend row label accounts only by position: 1, 2, 3, 4. A user with four Claude accounts cannot tell which segment is which account without hovering each one, and at narrow widths the number is the only thing the segment shows. The identity mark already exists in the code (AccountAvatar / ProviderInstanceIcon) and is already drawn in the segment popover; the bar just does not use it.
Impact
Cosmetic issue
Version or commit
main @ 50ff4c371e (0.0.40)
Environment
macOS desktop app (web renderer), dark theme. Also reproducible in the browser client.
Logs or stack traces
No response
Screenshots, recordings, or supporting files
Before — position numbers are all the bar exposes for identity:
![]()
After — the account's own mark (provider glyph + accent initials badge):
![]()
Same, wide layout:
| Before | After |
|---|---|
Captured against a synthetic four-account pool; the numbers are the only account identity the bar currently renders.
Workaround
Open each segment's popover to read the account. There is no in-app way to label the bar.
Related issues
- #11562 — initials badge obscures the provider logo in the Usage Limits popover. Related but different: that is the badge sitting over the glyph in the popover; this is the bar using no identity mark at all. A fix here should keep the badge legible, since it is the same
ProviderInstanceIcon. - #11641 — badge initials invisible on light accent colors. Same component, orthogonal.
- #11515 — Usage misreports limits with multi-account routing. Data, not presentation.
Not a duplicate: no existing issue or PR changes the pooled bar's account labels.
Suggested fix
Reuse the existing mark instead of the number: web's AccountAvatar in apps/web/src/components/usage/UsageLimitsPooled.tsx, mobile's ProviderInstanceIcon in apps/mobile/src/features/usage/UsageLimitsPooled.tsx. Small, no new component. A PR follows.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading apps/web/src/components/usage/UsageLimitsPooled.tsx and apps/mobile/src/features/usage/UsageLimitsPooled.tsx, then trace how pooled segments and legend rows receive their labels. Reuse the existing account identity marks described in the issue, preserving the provider glyph and initials badge. Done means each account is identifiable in the bar and legend at narrow and wide layouts without opening a popover.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, mobile-dev
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 85/100