[Feature]: Show usage for all configured Claude/Codex providers (not just the default ones)

[Jardo-51]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

apps/web

Problem or use case

I have multiple Claude code providers (work, personal, etc.) with different values of CLAUDE_CONFIG_DIR path.

The page currently only displays usage for the Claude provider with default path (~/.claude). I cannot see the usage from other providers.

Proposed solution

Read and display usage for all configured providers. Show a separate chart and stats for each provider (Claude Personal, Claude Work, etc.)

Why this matters

Users who have multiple Claude / Codex providers can only see usage for those on a default path.

Smallest useful scope

Extract the provider paths from all configured providers and read / display data for each one separately.

Alternatives considered

No response

Risks or tradeoffs

No response

Examples or references

No response

Contribution

• I would be open to helping implement this.

[watzon]

Glad I found this. Pretty much one of two issues I have with t3code currently, which admittedly is not that many issues.

For context I use cloak to manage multiple claude code accounts, so my work and home profiles are both in ~/.cloak/profiles. I've added both to t3code which is awesome, but the stats page shows no Claude usage at all because the profiles aren't being taken into account.

[Jardo-51]

Survey of the PRs that touch this, as of main at 6a9d9f9 — none of them have merged, so the behaviour described above is still current: UsageService.resolveTranscriptDirs resolves exactly one directory per provider from the legacy settings.providers.claudeAgent / settings.providers.codex blobs, and settings.providerInstances is never consulted.

None of these PRs reference this discussion (or #5791 that it was converted from); they were all filed against the sibling bug reports #7514 and #5805.

Part 1 — scan every configured instance (the "zero usage" half, which also covers @watzon's ~/.cloak/profiles case)

• fix(server): usage counts every configured provider instance #8470 — open, newest and most complete. Adds a usageProviderHomes module built on deriveProviderInstanceConfigMap, so the scan sees exactly the instances that can spawn agents; covers Claude, the Codex shadow layout and Grok, and reworks the cross-environment merge to claim ownership per provider.
• fix(usage): usage no longer misses custom provider-instance homes #5806 — open since August, same fix in a smaller shape (usageHomes.ts, dedupe by realPath).
• Six further closed, unmerged attempts at the same thing: #8276, #7419, #6603, #6596, #6312, #5735.

Part 2 — separate, labelled series per instance (what this discussion actually asks for)

• feat(usage): split usage per provider instance home #5738 is the only PR that implements it: UsageBucket carries homePath + homeLabel, UsageSource carries label, and the page renders one series per home named after the configured instance (e.g. Codex · Personal). It was stacked on fix(usage): usage no longer misses custom provider-instance homes #5806 and stayed draft waiting for it to land; fix(usage): usage no longer misses custom provider-instance homes #5806 never landed, so this is currently orphaned.
• #6603 covered part of the attribution via a sourceIndex on each bucket.

So part 1 has seven competing implementations and needs a maintainer to pick one, and part 2 has no live PR at all. Happy to rebase the labelling work on top of whichever part 1 lands.

_{Closed PRs are written as code spans rather than links to avoid cross-reference noise on abandoned branches.}