What is this?
A local-only tool to log your visible “usage %” and estimate depletion ETA using burn rate. Even if official caps are opaque, burn rate gives you a practical pacing signal.
Quick start
- On Dashboard, enter 5h% / Weekly% and click Save
- Log at least twice (e.g. morning + night)
- See burn rate and depletion ETA
You can log weekly only. 5h% is optional.
Burn profiles (filters)
Burn rate changes by workload (big PR vs tiny edits). Tag logs with mode / status / model / note, then filter to forecast the current situation.
- mode: cloud / cli / local / other
- status: your own memo is fine (ok/warn/limited/cooldown)
- model: mini/high etc (if known)
- note: “search-heavy”, “big PR”, etc
“Forecast uses filters” = yes uses only filtered logs for prediction.
Resets (window renewals)
Sometimes reset happens before depletion. When likely, the subline says so. Auto estimation is heuristic; manual pin is the most accurate option.
Profiles
Save current filter state as a named profile. Duplicate names overwrite (no duplicates).
FAQ
Q. If caps are unknown, is this useful?
A. Yes. Burn rate (%/h, %/day) is actionable pacing information even without absolute caps.
Q. What should I log?
A. Weekly% is often the main constraint. Log 5h% when you need short-horizon pacing.
Q. What is “status”?
A. It can be your own label. Use it to separate situations where burn rate differs.
Q. Does it upload my data?
A. No uploads. Logs/profiles/settings stay in localStorage. (Analytics/ads are for page views.)
Known limitations
- This does not reveal official caps; it estimates from burn rate.
- Few logs = noisy rate (2 minimum; 5+ recommended).
- Workload/model changes can shift burn rate suddenly.
- Reset estimation is heuristic; pin manually if you can.
- localStorage is per browser; use Export/Import for migration.