Quota & fallback
Out of quota doesn’t have to mean out of work
When Codex runs out of quota halfway through a task, Pyloxa stops sending it work and offers the fallback from your rules. You confirm, and Claude Code continues from the files Codex already changed. Or wait for the reset and let the original agent carry on.
- 70% · 90%Claude Code usage that turns the title bar yellow, then red
- 2Takeovers per task, at most
- 3Automatic runs per task, at most
- 0Automatic switches from a subscription to an API key
See what’s left in the title bar
Turn on “Show agent usage in the title bar” to see how much of your Claude Code subscription is left. It shows the tighter of the 5-hour and 7-day limits.
- Yellow at 70% used, red at 90% or when you’re limited, and “—” before there’s any data.
- The numbers come from the usage events Claude Code reports while it runs. Pyloxa makes no extra queries, so the meter updates after a run.
- Codex doesn’t report its subscription quota, so it shows only today’s tokens and appears in the title bar only when it’s limited. API-key connections and Gemini CLI also show only today’s tokens.
- Pyloxa reads no credentials, and quota numbers stay on your computer.
When quota runs out, you decide who takes over
When a CLI reports that its quota is used up, Pyloxa marks the connection as limited and sends it no work until the reset time, or until you click “Quota restored”. In the free version, you confirm each takeover.
- Another CLI takes over: following the fallback in your rules, the next agent continues from the files the previous one already changed.
- Retry when the quota resets: starts automatically when the reset time is known; otherwise it waits for you to click “Quota restored”.
- Each task runs automatically at most 3 times and changes hands at most 2 times, and never goes back to an agent that already failed it.
- A short rate limit (5 minutes or less) is retried once; a network error is retried once after 30 seconds.
- Automatic takeovers only move to a connection with the same billing source: work on a subscription never switches to API-key billing on its own.
Pro: automatic takeovers, and quota used your way
If you’d rather not confirm every time, Pro takes over along the fallback chain in your rules, and lets you decide which project uses quota first and when work starts.
- Automatic fallback when quota runs out: off by default and fixed when you approve a plan. It triggers when quota runs out or a task is waiting on a limited connection, with the same limit of 2 takeovers per task.
- Priority and quota per connection: set which projects go first and give each connection an estimated quota. Quotas are estimates, not provider limits, and not billing evidence.
- Scheduled start: start a whole plan after the next quota reset, or at a set time up to 30 days ahead. Up to 30 minutes late it still starts; later than that it waits for you. In the 24 hours before the start, the computer won’t sleep while it’s plugged in.
- Backup brains: up to 3. If the brain’s service fails, Pyloxa retries once, then hands planning to the next brain for 10 minutes.
- Usage and hours: a usage dashboard across projects, exportable as Markdown or CSV.
Free and Pro
Both keep work going when quota runs out. The difference is whether you confirm each time, and whether you can plan ahead.
| Free | Pro | |
|---|---|---|
| Seeing usage | Agent usage in the title bar, usage for each run | Adds a usage dashboard and reports across projects |
| When quota runs out | A fallback you confirm each time, or a retry after the reset | Takes over automatically along your fallback chain |
| Planning ahead | Tasks waiting on quota resume after the reset | Priority, quota per connection, scheduled start |
| Brain | One brain, which you can change any time | Up to 3 backup brains |
| Notifications | Windows desktop notifications | Adds Telegram, Discord or a webhook |
Questions
How does Pyloxa know how much Claude Code quota is left?
Claude Code reports usage events while it runs, and Pyloxa reads those. It makes no extra queries and reads no credentials, so the title bar updates after a run and shows the tighter of the 5-hour and 7-day limits.
Why does Codex show only tokens?
Codex doesn’t report how much of the subscription is left while it runs, and Pyloxa doesn’t query Codex’s quota any other way. So Codex shows today’s tokens, and the title bar flags it when it’s limited.
When another CLI takes over, does it start from scratch?
No. The agent that takes over continues from the files the previous agent already changed. A task changes hands at most 2 times and never goes back to an agent that already failed it.
Will Pyloxa switch to paid API usage when quota runs out?
Not on its own. Automatic takeovers only move to a connection with the same billing source, so work on a subscription never switches to an API key by itself; moving work to an API-key connection is your call. Pyloxa doesn’t resell or proxy any AI service, and all usage counts against your own subscriptions or API keys.
Try it on your own project
Pyloxa is a free Windows app. It runs the Claude Code and Codex CLIs you already use, on your own subscriptions or API keys.