Optional pinned cross-provider allowance summary in the thread header

[zds-xiaoxin]

Problem

When deciding which configured agent to use next, I want to compare a few subscription allowance windows without leaving the conversation or repeatedly opening Usage. I use T3 Code with several providers, and the choice depends on which account still has allowance in the window I care about.

T3 already provides Usage → Limits and configurable thread-detail usage information. I read the maintainer replies in #11563 and #13241, closed after #26859 shipped Usage in thread details; those replies invite a new idea for remaining needs. The remaining need here is comparing several selected provider/accounts at once before choosing the next agent, rather than showing only the current thread provider. This proposal is about keeping a small user-selected subset visible in the conversation header, not collecting new quota data or replacing those views.

Concept mockup

Concept only, not a shipped feature or implementation acceptance evidence. AI-edited from the official public marketing screenshot; all added account labels, quota values and reset times are fictional. Progress indicators and placement are illustrative.

The two pinned header entries make different providers/windows visible at once. Clicking an entry opens account-specific detail; an unavailable reading stays unavailable rather than displaying 0%. Final wording, placement and surface support would follow maintainer direction.

Smallest useful scope

An optional compact header summary, off by default, with a few pinned account/window entries:

• Select an existing reported account and one of its actual windows (for example its session or weekly window).
• Show provider/account identity and remaining percentage. Each entry retains its own window label; mixed session and weekly selections must not be labelled as all weekly.
• Open the existing limits detail from an entry for reset time, last checked time and full account information.
• Keep unavailable distinct from 0% remaining. Clearly mark stale readings, and never turn an elapsed reset time into an invented refreshed allowance.
• Collapse gracefully on narrow screens and let users hide/reorder entries. Do not cover the thread title, controls or approvals.

Example with fictional data: Codex · account 1 · weekly 62% and Claude · account 2 · session 35%. These are independent windows, not percentages that can be added together.

Boundaries

Reuse the existing provider-reported allowance snapshots, account identity and refresh behavior. No extra periodic provider probes, new authentication, pooled percentage, automatic account switching, quota enforcement or cost prediction. Existing Usage views remain the source for details. A first implementation could be limited to shared web/desktop, with the mobile layout decided explicitly before implementation.

Local prototype and direction question

We have used a local customization with compact header entries, account/window selection and cached/unavailable states. It makes allowance easier to consult while choosing an agent. That implementation is not an upstream-ready patch, and no upstream validation or maintainer approval is claimed. I have not attached real account screenshots or private usage values.

Would this fit as an optional presentation of the existing Limits capability, or should the same need be handled through the thread details card? If the direction is welcome, I can prepare a focused PR against the agreed entry point and scope.

Prepared with GPT-6.1-Sol through the Codex harness in T3 Code on behalf of the account owner.