The Claude Code usage tracker for people with more than one plan
ResetOwl reads every Claude Code and Codex login on your computer, shows what each plan's limits have left and ranks the accounts so the allowance that expires first gets used first.
Why one Claude Code login is no longer the whole picture
Plenty of developers now pay for more than one AI coding plan: a personal Claude plan, a work seat, a ChatGPT plan for Codex, maybe a spare account for side projects. Each one meters usage in its own windows and resets on its own clock. The CLI shows you the login you are signed into, one at a time, so the question that matters — which of my accounts should I be using right now? — has no answer anywhere.
The cost of not knowing is quiet. A weekly allowance you paid for resets unused while you burn through another account’s 5-hour window and hit a limit mid-task.
What a Claude Code usage tracker should show
A useful tracker answers four questions for every account, not just the current one:
- What is left in each limit window: the 5-hour session window and the weekly one.
- When each window resets, so you know what expires first.
- Which account to use next, taking both into account.
- What the usage is worth, so you can tell whether a plan pays for itself.
How ResetOwl tracks your usage
ResetOwl is a desktop app. It finds the Claude Code and Codex logins already on your computer and, for each one, asks the provider for its limit windows: Claude Code’s own usage endpoint, and for Codex the Codex CLI itself, falling back to its ChatGPT usage endpoint and to the rate limits Codex writes in its session logs. Each login’s credentials go only to the provider that issued them.
Tokens are counted from the CLIs’ own transcripts, per model and per day, and priced at the vendors’ API rates. That is how the pricing guide can compare a plan’s price with what the same usage would cost on the API.
The account to use next
The queue ranks every account by headroom per hour before its reset: an account with 40% left that resets in two hours should be used before one with 70% left that resets in five days. ResetOwl puts that account at the top of the list and in your menu bar.
When you decide to switch, marking an account as in use writes a small pointer file. An opt-in shell snippet makes claude and codex in your terminal follow it, and you can remove it at any time.
Adding more accounts
Add account signs a new login into its own folder with the provider’s own CLI (claude auth login, codex login), so a second login never signs the first one out. Use the accounts you hold under each vendor’s terms: personal and work seats, or plans you pay for yourself.
Renewals and what expired unused
Providers do not report a billing day, so you set it once per account. ResetOwl then shows a calendar of renewals and, on the overview, how much paid allowance expired unused in the last month.
Frequently asked questions
Does ResetOwl send my Claude Code credentials anywhere?
No. Provider tokens never leave your computer except to their own provider, and ResetOwl never refreshes them. Only account emails, plan names, limit percentages, reset times and token counts reach ResetOwl.
Can I track Claude Code and Codex in the same place?
Yes. ResetOwl reads both CLIs' logins and puts every account in one queue, ranked by how much headroom each has per hour before its next reset.
How often does ResetOwl refresh my usage?
Every ten minutes, with back-off, and it pauses for 15 minutes when a provider answers with a rate limit.
Does it work with the Ultra plan, which has no 5-hour limit?
Yes. The plan catalog knows which plans meter a 5-hour window and which only meter a weekly one, and the queue uses whichever windows each plan has.
What does it cost?
ResetOwl is free and open source under the MIT licence, for macOS, Windows and Linux.