Quick answer
UsageAtlas shows supported rate limits, credit allowances, and reported resets for Codex, Claude Code, Cursor, GitHub Copilot, Warp, Kimi Code, Kilo Code, Factory / Droid, Amp, and Qoder. Capacity meters and alerts need a known allowance. The app is free and open source.
Read each usage window separately
Claude Code reports a five-hour window and a weekly cap. Codex reports session and weekly windows. Cursor reports plan, Auto + Composer, and API usage from the signed-in desktop session.
UsageAtlas shows the supported windows that are actually available on this machine. Provider numbers can lag. Confirm a hard stop in the provider account if you are about to miss a deadline.
One alert, then quiet
Pick a remaining-capacity threshold per window. UsageAtlas sends one notification in that reset cycle. It will not stack five toasts while you are in a diff.
OpenCode, Antigravity CLI, Pi / OMP, and Muse Code contribute local activity. These integrations do not provide quota windows, reset clocks, or limit alerts.
Questions, answered
Can I see AI usage limits and reset times?
Yes, when a connected provider reports a supported window and reset. This includes available limits from Copilot, Warp, Kimi Code, Kilo Code, Factory / Droid, Amp, and Qoder as well as Codex, Claude, and Cursor.
Do the local-history sources have rate-limit windows here?
No. OpenCode, Antigravity CLI, Pi / OMP, and Muse Code add local tokens, requests, models, and sessions. Their UsageAtlas integrations do not collect subscription limits or reset times.
Are limits guaranteed live?
No. Providers can delay or change reported windows. Treat this as a planning view.