← Back to the overview
Reset alerts
The notifications
An interruption has to earn itself. Four of these are worth being interrupted for because quota came back and you would otherwise find out by trying; three are worth it because something changed that you cannot see from the screen you are on.
The four resets
- ✓Surprise! — your weekly limit reset ahead of its scheduled deadline, a known Claude Code quirk worth catching.
- ✓Bonus! — a partial mid-window credit dropped your weekly usage. Found money.
- ✓New week! — the calm, routine weekly reset.
- ✓Fresh session! — the 5-hour window rolled over, fresh for the next five hours.
- ✓All four carry a confetti burst and the quota bar visibly refilling, all four are on by default, and each is toggled independently in Settings.
The three without confetti
- ✓Heavy startup context — a project's instruction files, memory and skills have grown enough that every session pays for them before you type a word, with what it costs to load on a cold cache. At most once per project per week, and off by default: nobody asked to be told their own files are growing.
- ✓Extra usage has started — it exists because the four above do. The app interrupted you to say quota came back and said nothing when you started paying. Fires once when a check first finds you past your included quota; not on a timer, not again while the same spell lasts. A receipt, not a prompt: it names no account and suggests nothing.
- ✓Profile set for Windows — writing the machine-wide profile is the least visible thing this app does, so it confirms itself: only when you switch by hand, once per switch, and only after the variable is read back to check the write took. Deliberately no quota bar — a bar animating one account's remaining quota into another's would suggest switching accounts because one ran out, and this app does not say that.