1. Read remaining usage and reset time together
A low percentage may be manageable when reset is close, while a healthy-looking percentage can still be risky if the weekly reset is days away and the next task is large. Separate the active session allowance from the longer weekly allowance.
2. Make tasks smaller in the risk zone
- Finish work at a file or feature boundary before starting a broad refactor.
- Save and verify current changes before opening a long new context.
- Keep research, documentation, and testing tasks available for a tool switch.
- Near reset, favor review and cleanup over opening a large unfinished branch.
This does not increase quota. It reduces the amount of unfinished work left behind when a limit interrupts the session.
3. Lower the cost of checking
Opening several dashboards can become its own interruption. RunDog uses runner speed for routine awareness and keeps exact Claude and Codex values in one popover. Usage refreshes every 60 seconds, pauses while the Mac sleeps, and can be refreshed manually.
- Normal work
- Glance at the runner
- Runner speeds up
- Open remaining usage and reset time
- Limit reached
- Move to a prepared task until reset
What the current version does not claim
RunDog currently shows provider-reported remaining usage and reset times. It does not predict an exhaustion time from your recent burn rate. The interface avoids presenting an estimate as a measured fact.