Factory Droid usage limits on Pro, Plus and Max work as three rolling windows, 5-hour, 7-day and 30-day, and you need room in all three before Droid will send a request. When the Standard pool runs dry you can switch to the separate Droid Core pool or turn on Extra Usage, and a free tracker such as UsageAtlas keeps every window and its reset in view on your desktop.
The three rolling windows
Individual plans use rolling Rate Limits, not one monthly bucket. Each window starts counting when you first use Droid and resets once that window has passed. They run independently: filling the 5-hour window does not drain the 7-day or 30-day one any faster, and the reverse is also true.
A request goes through only when every window has headroom, so a busy afternoon can stop you with most of the month left.
| Window | Length | What usually trips it |
|---|---|---|
| Short | 5 hours | A long agent run or several parallel sessions |
| Weekly | 7 days | Steady heavy use across a working week |
| Monthly | 30 days | Sustained use over the whole period |
Factory does not publish fixed allowances for each window, and the amounts can change, so the useful number is the one your own account reports.
Standard Usage and Droid Core
Your plan has two pools. Standard Usage is spent first and covers the frontier models Factory offers. Droid Core is a set of open-weight models with its own, separate Rate Limits. Factory's docs say enabling Core costs nothing extra; it draws on the same billing but only lets you pick Core models, so you can keep working after the Standard windows are spent.
Each model also has a multiplier on Factory's models page, so heavier models drain Standard Usage faster than lighter ones.
What happens when you hit a limit
The request in progress finishes. The next one returns a Rate Limit error in the CLI or the Factory App. From there you have three choices:
- Run
/limitsin Droid and switch to Droid Core. - Turn on Extra Usage, prepaid USD credit that does not expire and stays on until you turn it off or it runs out.
- Wait for the window that ran out to roll forward.
Missions follow the same Rate Limits, need Extra Usage enabled, and pause when they hit a limit. Unused Standard Usage does not roll over to the next month; purchased Extra Usage does.
Teams seats each get Pro Rate Limits. Business and Enterprise accounts use custom limits under contract instead of the rolling model, so this guide applies mainly to individual plans and Teams seats.
Track Factory Droid usage limits with UsageAtlas
Factory's own views are /limits in Droid and Settings > Usage in the app, which may be enough if Droid is your only agent. If you also run Claude Code, Codex or Cursor, checking each screen gets old fast.
UsageAtlas is a free, open-source desktop app for Windows, macOS and Linux. Add a Factory API key under Settings > Sources, choose Save and check, then open Limits. It shows the Standard and Core windows as separate meters, any extra balance, and reset times when Factory supplies them. You can set an alert on a supported window so you hear about a low pool before Droid refuses a request.
Two honest limits on the integration: it reads account capacity, not Droid's /stats history, so per-session tokens stay in Droid. And it never merges unrelated pools or invents a percentage when Factory leaves an allowance out; a missing limit shows as unknown. Read the Factory setup steps for the key options.
Questions
Why does my account show older Standard or Premium counters?
Some Factory accounts still return an older billing format. UsageAtlas supports selected legacy counters as well as the newer Standard and Core windows.
Does a missing reset time mean the window never resets?
No. It means the response did not include a usable reset time. Check Settings > Usage in Factory for that window.
Do the limits differ between Pro, Plus and Max?
Yes. Plus and Max come with expanded rolling Rate Limits compared with Pro. Factory's pricing page has the current comparison.