Show token usage and estimated cost per thread

[stoivo]

I’d like to see how many tokens each thread has consumed and its estimated cost, so I can understand the expense of individual tasks and compare model choices.

Ideally, each thread would have a compact usage summary showing:

• Total token usage, with input, output, and cached tokens where available.
• Estimated API cost, clearly distinguished from actual billed spend for subscription accounts.
• A breakdown by model when multiple models are used in the same thread.

A thread breakdown on the Usage page would also be useful. Maybe link from the thread too.

It has been implemented in #9017 but I want to open a discussion in case PR gets closes or too stale.

It think the UI implemented looks fine.

Related work:

• feat: add usage / quota visibility for Codex sessions and accounts #228 previously requested per-thread usage alongside account quotas.
• feat(usage): add thread and subagent breakdown #9016 proposes thread and subagent breakdowns on the Usage page.
• feat(web): show thread API cost in composer #9136 proposed a thread cost indicator in the composer and was closed pending the V2 rewrite.

Could this issue track the feature request through V2, independently of those implementation PRs?

Also somewhat related to #6683

[pantharshit007]

posting for ref

[ZaBug]

+1. Folding in details from my closed duplicate #15043 (V2-specific):

• Cost source priority: prefer the provider-reported figure (Claude's result total_cost_usd, the same number the CLI status line shows), fall back to the LiteLLM estimate (with usagePriceOverrides), and label which one is shown.
• Placement: a "Thread cost" row in the existing Context Window popover under "Total processed", plus an optional compact composer badge ($1.4 · 32%).
• Settings in the UI (Settings → General, next to the context window indicator): show thread cost, show composer badge.
• Budget line: when a gateway budget source is configured (Generic HTTP `usageLimitSources` kind for gateway / proxy spending budgets #15042), show "Monthly budget $42 / $1000" in the same popover.
• Open question: total_cost_usd is cumulative per CLI session and resets on resume. Sum across sessions, or switch to the estimate?

[ajbarryiii]

I’d like to contribute a narrowly scoped version of this for V2. I run multiple long-running threads and want to see which threads account for my usage.

The proposed UI would mirror the existing Hour breakdown: one row per thread, showing its name and either estimated cost or tokens according to the existing metric toggle. A green dot would indicate threads that are currently running. It would reuse the existing period and environment filters.

I would leave out subagent drill-downs, project reporting, additional charts, and custom date controls. Usage that cannot be reliably attributed would remain explicitly accounted for.

Would a maintainer approve this direction and scope for a contribution before I start implementing it? Are there any constraints or existing work you would prefer me to build on?

[ZaBug]

Follow-up to my comment above with a working V2 prototype (dummy data, local mock):

Before / after: Context Window popover

• Thread cost prefers the provider-reported figure (Claude's total_cost_usd, stored per turn as a delta so resumes don't double-count) and falls back to an estimate at Usage prices with usagePriceOverrides. The label says which one is shown.
• Optional composer badge ($1.00 · 6.8%), off by default.
• The Monthly budget line only appears when a gateway source from Generic HTTP `usageLimitSources` kind for gateway / proxy spending budgets #15042 is configured.

Settings → General, next to the context window indicator:

This complements the per-thread breakdown on the Usage page proposed above; it answers "what has this conversation cost" from inside the thread. Happy to scope a PR to just the popover row if a maintainer approves.

[pantharshit007]

@juliusmarminge @t3dotgg @maria-rcks can anyone look into this, we can include this in the V2 stable release.