feat: add usage / quota visibility for Codex sessions and accounts

[Fanzzzd]

I’d like T3 Code to surface usage information so users can better understand cost/rate-limit consumption while working.

Why

For long-running coding sessions it is hard to tell:

• how much usage a thread consumed
• whether the current account is close to rate limits
• whether a model/service-tier choice is still appropriate

Requested scope

• Show per-thread or per-turn token usage when available.
• Show account-level rate limit / credits / quota information when available from the provider.
• Add a lightweight usage summary in the UI, ideally without overwhelming the chat view.

Suggested UX

• Thread-level token usage near the thread/session metadata
• Account usage summary in sidebar or settings/account area
• Refresh or auto-update on relevant provider events

Suggested acceptance criteria

• Users can inspect current thread/session usage without opening logs.
• Users can inspect account-level quota or rate-limit status when the provider exposes it.
• The UI degrades gracefully when the provider does not expose usage data.

Relevant code context

• apps/server/src/codexAppServerManager.ts
• apps/server/src/provider/Layers/CodexAdapter.ts
• apps/web/src/components/ChatView.tsx

Reference implementation ideas

• CodexMonitor exposes local usage snapshots, thread token usage, and account rate-limit views.
• Codex app-server events include account and token-usage style notifications that look relevant to this problem.

[maria-rcks]

Not planned at this time. If yall have any examples of similar open sources apps doing it well, share them here.

[nassimna]

This is important, and every app should have this since it's important to switch threads every time you reach the window context limit, because most of the models lose accuracy after compact
the best example is codex and every CLI

[maria-rcks]

@nassimna im mainly talking about usage visibility, sorry for not being clear on my previous message

[Sayrix]

A pie chart, similar to what GitHub Copilot uses, might fit well with the current UI of T3 Code.

[Aditya190803]

@Fanzzzd @maria-rcks

I’ve implemented this for Codex and I’m planning to open a PR. It looks like an L-XL sized change, and I’ve attached screenshots for context.

I should mention I’m currently unvouched, so please let me know if that affects whether you’d like me to open the PR.

This is the settings panel:

This is the ContextWindowMeter:

[juliusmarminge]

I don't think we need to expose it in the chat view, it just feels awkward to have it when you hover a gauge which shows 35 to see aa completely unrelated percentage for a completely unrelated metric.

but i do think we could expose it under the provider view. UI there could probably use a little work to expose both the session and weekly limits. and we should do it for claude as well!

if ur up for it i can review the pr

[Aditya190803]

Sure, I can take that on.

Could you clarify what you mean by session limits?
Are you referring to the context window or something else.
@juliusmarminge

[juliusmarminge]

both codex and claude have 2 buckets, one burst (often referred to as session limit) and one weekly