Windows, not vibes
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 is local activity, not a provider quota window, so it shows up in tokens and history rather than a reset clock.
Questions, answered
Can I see AI usage limits and reset times?
Yes, for supported Codex, Claude, and Cursor windows. Remaining capacity and local reset time are in the dashboard.
Does OpenCode have a rate-limit window here?
OpenCode is tracked as local tokens, requests, models, and sessions. It does not expose the same provider reset clocks as Claude or Codex.
Are limits guaranteed live?
No. Providers can delay or change reported windows. Treat this as a planning view.