​

Usage and cost caps

Each project has rolling 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. If the project uses BYOK, those calls go to your provider account and do not count against the Qodex-funded cap.

​

How rolling caps work

This means you do not need to wait for midnight or Monday. The countdown tells you when enough usage will roll off.

​

Where to see usage

Open Settings > Plan in a project. You will see:

• Current plan.
• 5-hour usage.
• 7-day usage.
• Time until headroom returns.
• Which usage is Qodex-funded and which is BYOK.

The chat cost view 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.
2. Add BYOK so new calls route through your provider key.
3. 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