Quick answer
Factory Droid measures usage over rolling windows rather than resetting on a calendar date. That means older usage drops out continuously and capacity returns in slices, so a blocked request can succeed later without waiting for a monthly reset. The account panel shows the current window and remaining allowance for your plan.
Rolling vs calendar
| Model | Reset behaviour | Practical effect |
|---|---|---|
| Calendar month | One date refills everything | All-or-nothing at the boundary |
| Rolling window | Old usage ages out | Capacity returns gradually |
| Multiple windows | Short and long layered | Bursts recover faster than sustained load |
| Balance-based | No reset | Only a top-up restores capacity |
Rolling windows reward pacing. If you drain a window in an hour, you wait for that hour's usage to age out. If you spread the same work across a day, you rarely hit the ceiling.
Read your window
- Open the Factory account panel and find the usage section.
- Note which window the percentage refers to.
- Check whether more than one window applies to your plan.
- Record the remaining amount before a long agent run.
- Re-check after the run to learn what it cost.
Plan agent work around it
- Split large refactors into scoped sessions that finish.
- Avoid parallel agents competing for the same window.
- Stop a run that repeats the same failing step.
- Keep a fallback tool for the hour a window is empty.
- Track local tokens to know what a task really consumes.
UsageAtlas shows Factory's reported usage beside local session history, so the rolling window and the token cost are visible together. For the plan differences, see Factory Standard vs Core.
Questions, answered
What is a rolling window in Factory Droid?
A moving period of usage. Old requests age out continuously, so capacity returns gradually instead of at a monthly reset.
When does Factory Droid usage reset?
There is no single reset date for a rolling window. Capacity returns as earlier usage leaves the window.
Why am I still limited after waiting?
The window may not have aged out enough usage yet, or a longer window also applies. Check the usage panel rather than guessing.