​

Usage and cost caps

Each project has caps on Qodex-funded LLM spend. The caps protect your project from accidental runaway usage. They apply only when Qodex is paying for the provider calls. Calls on the project’s own OpenAI key (BYOK) or its own connected ChatGPT subscription are paid by your account and never count against the Qodex-funded caps.

​

How the caps work

The two rolling windows have no fixed reset. Headroom returns continuously as old usage leaves the window, so you do not need to wait for midnight or Monday. The countdown tells you when enough usage will roll off. Other monthly quotas, such as included pull request reviews, also count per calendar month in UTC.

​

Where to see usage

Open the account menu at the bottom of the left navigation, then choose Usage. You will see:

• The current plan, next to the page heading.
• A 5-hour limit bar.
• A Weekly bar.
• A Monthly bar.

Each bar shows the percentage of Qodex-funded usage and when headroom returns. A window with no cap on your plan reads Unlimited. The chat composer also shows usage while you are working with the agent.

​

What happens at the cap

When a project reaches its cap:

• New chat runs pause with a clear cap message.
• Scheduled runs and PR reviews wait until headroom returns.
• In-progress runs stop at a safe boundary, save partial work, and mark the run as budget_exceeded.

budget_exceeded is separate from a test failure. It means the run stopped because of budget, not because the app failed.

​

Per-run budget

Each test run also has its own token budget. The project cap protects the whole project. The per-run budget protects one scan from consuming too much context or cost by itself. At 80%, Qodex warns. At 100%, the run stops, saves partial output, and marks the run budget_exceeded.

​

How to get unstuck

If you hit a cap:

1. Wait for usage to roll out of the window, or for the new month.
2. Add BYOK so new calls route through your provider key.
3. Connect your own ChatGPT subscription in Settings > LLM keys.
4. Upgrade the project plan.

For heavy security, exploration, or PR review work, BYOK is often the cleanest way to keep runs moving while retaining your own provider-level spend controls.

​

Next steps