Usage limits: show if the current pace lasts until reset, and by how much

[Dwite]

The problem

Usage → Limits shows how much quota is left and when the window resets. It also shows a pace arrow (ahead / on / under) and a line on the bar for even spending.

The math is still on me. With 40% of the weekly limit left and 4 days to go, I do not know:

• Will I run out before the reset? When?
• If yes, how much am I short?
• If no, how much will I have spare?

The arrow says "ahead of pace" but not by how much. Its words show only on hover.

The idea

Add one short line of text per limit window. It says what happens if I keep the same speed.

Examples for a weekly window, 3 days in:

Used so far	Line shown
60%	At this pace: runs out in 2d, 2d before reset. Needs ~40% more quota.
43%	On pace. Lasts until reset.
30%	At this pace: ~30% unused at reset.

The math uses only values the app already has: percent used, reset time, window length.

• Speed = percent used ÷ time since the window opened.
• Run-out time = percent left ÷ speed.
• Shortfall or spare = speed × full window, compared with 100%.

Where

• Usage → Limits page (web and desktop).
• /usage-limits panel in the composer.
• Limits section on mobile.

The math goes in packages/shared/src/usageLimits.ts next to paceOf, so all clients agree. No contract change. No server change. No new setting.

Limits of the estimate

• It is a straight-line guess from the average speed since the window opened. Real use comes in bursts.
• Early in a window the guess is noisy. Proposal: show nothing until 10% of the window has passed.
• Windows without a reset time or a length show nothing, same as the pace arrow today.

Related

• Show the even-pace point on Usage → Limits bars #11120 puts an even-pace tick on the pooled bars. That shows where even pace is. This idea says what happens next, in words. Neither needs the other.
• Show remaining 5-hour and weekly subscription limits as percentages in the top bar (100%/100%) #11563 and Show usage headroom for the active model outside the usage limits panel #13241 show limits in more places. This idea does not add places.

Questions for maintainers

1. Is the direction OK?
2. Text line under each bar, or only in the bar tooltip?
3. All windows, or weekly only? The 5-hour window may be too short for a useful guess.
4. Pooled bars with several accounts: one line per pool, or per account?
5. Optional extra: a daily budget hint, e.g. Stay under 10%/day to last (now 20%/day). Wanted, or too much?

I can build this after you approve direction and scope.

[AdEx-Partners-DE]

I wanted exactly this line, so I built it in my fork today, and it is as useful as you describe.

Under each window in Usage → Limits there is now one sentence: "At this pace empty ‹time›, before the reset ‹time›" or "At this pace N% stays unused at the reset ‹time›". In my dev build with real data seven windows showed a line, and one of them was the "empty before the reset" case, which I would not have spotted from the bar.

One difference from your proposal that may be worth discussing: I do not use the average since the window opened. The fork records each reading over time (see #18180), so the pace comes from the readings since the last reset, and a line only appears once there is an hour of data in the current cycle. That copes better with an early reset, where "time since the window opened" is no longer what the provider announced. The price is a server-side record; your version needs none.

The run-out wording answers "when". Your "needs ~40% more quota" answers "by how much", and I do not have that yet. I think yours is the better sentence.

Which would people rather have: the simple average with no storage, or the recorded pace?

Code: ac604af15 on stark/main, four tests.

---

Posted by Claude (Opus 5.5, Claude Code via T3 Code) on behalf of @AdEx-Partners-DE.