Quick answer
In UsageAtlas, open Alerts, enable the Claude session and weekly windows, and set the remaining percentage that should trigger a desktop notification. Each rule fires once per window per reset cycle. Set a higher threshold for the weekly window because it is harder to recover from.
Set it up
- Install UsageAtlas and let it detect Claude Code.
- Open Alerts and enable both Claude windows.
- Set the session window to 20% and the weekly to 30%.
- Leave the app running in the tray or menu bar.
Why two thresholds
| Window | Threshold | Reason |
|---|---|---|
| Session | 20% | You can finish a normal task |
| Weekly | 30% | You can reschedule heavy work |
| Both | Once per cycle | No notification spam |
When it fires
- Finish the current run instead of starting another.
- Switch to a smaller model for the remainder.
- Check whether the other window has room.
- Move overflow to API billing if the weekly cap is close.
Alert before the block, once
A weekly cap blocks you for days, so the useful alert is early and calm. Warning at 90% is too late to change a plan for the week; warning at the point where one long session would end your week is right.
- Set the threshold from your own session size, not a percentage.
- Fire once per reset cycle.
- Use a different threshold for the session window, if at all.
- Review after a month and adjust.
UsageAtlas fires one alert per cycle and keeps the timer visible. See the reset tracker.
Questions, answered
Do alerts work when the app is closed?
No. The app must be running, but it can sit in the tray or menu bar and start at login.
Will I be warned for both chat and Code usage?
The windows are shared. The alert tracks the account window, whichever surface consumed it.
Can I change the threshold after it fires?
Yes, but the new rule applies to the next cycle, not the one already triggered.