Read the provider windows
- Open the user/account menu and look for Usage remaining.
- Inspect the provider and each reported usage window or reset time.
- Check the observation’s timestamp and freshness before relying on the value.
- Use the offered connect or reconnect action if the provider needs a usage connection.
- Return to the indicator after the connection completes and verify whether a fresh observation is available.
A usage connection and a coding CLI login can be separate steps. Cursor’s setup path specifically depends on a fresh usable usage response before enabling the harness. Other providers may expose different account windows or no usable observation at all.
Interpret missing and stale information
Unknown, unavailable, failed, or stale information does not mean zero usage, unlimited usage, or a reset. A displayed reset time describes the reported provider window; it does not promise that every model or request becomes available at that moment. Check the provider’s own account view if Rudr cannot obtain a fresh observation.
A model context indicator describes the current conversation’s input space. The Usage dashboard describes recorded activity and cost estimates. Neither replaces the account’s remaining allowance.
Continue when allowance is low
You can choose another ready harness for a new task. For existing sessions, Claude Code ↔ Codex continuation is available only between runs and sends bounded handoff context with the next message. Switching does not transfer credits, reset a provider window, or guarantee the destination model is available.
If the allowance display seems inconsistent, capture the timestamp, window label, route, and sanitized error through Diagnostics.