Limits over time: a 7-day line per account, and a log of every reset that shows what an early reset cost you

[AdEx-Partners-DE]

This morning both of my OpenAI accounts were reset three days before the announced date. One of them still had 30% of its weekly allowance unused. Gone.

I only know that because my fork had started writing the readings down the night before. In the stock app the bars would simply have shown 100% again, and I would never have known whether I had lost anything.

Usage → Limits shows now. It cannot tell you how you got here. So below the bars my fork adds:

• Last 7 days: one stepped line per account and window, flat while nothing is used, falling as the allowance is spent.
• Resets, listed under their account: when, how much was still unused, and early with the date it had been due ("30% unused · early, was due Wed, Oct 14").

Why this is worth having:

• You finally see the shape of your week. Did I burn it all on Monday, or does it last?
• Early resets become visible. They happen, they are provider-wide, and today they are invisible.
• It costs nothing extra. The service listens to the readings the app already takes and stores only changes, 120 days of them.
• It is the base for pacing. "At this rate it lasts until Thursday" (Usage limits: show if the current pace lasts until reset, and by how much #16009) is one step from here.

Checked: six tests for reset detection, and the real early reset above, shown with the right account, time and unused share. Open: mobile, a marker for the next reset on the line, and telling a provider-wide reset from a redeemed one.

Would a week of history change how you spread work across accounts? And has anyone else been bitten by an early reset?

If only one piece: the reset log

The line chart is the nice part, the reset log is the useful part. A first step could be the record plus the list of resets with their unused share, and nothing else: no chart, no forecast. The record is one server file that stores changed readings from the polling that already runs, so there is no database migration and no extra provider traffic. Maintainers, is that a shape you would consider, or does history like this belong outside the app?

Code: 1afd2b378, 5e7c61806. on stark/main.

---

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