docs

Budget

Caps per day and per week, and how they are counted.

nightaudit runs on the subscription you already pay for, which means the fastest way for it to become a problem is to burn through your quota. So it counts.

providers:
  claude_code:
    enabled: true
    budget:
      max_runs_per_day: 6
      max_runs_per_week: 30
  • Every attempt counts — including failures and timeouts. They spent your quota, so they cost budget. Counting only successes would let a broken project drain the account in a loop.
  • Both caps bind. Under the daily cap but at the weekly one? It stops.
  • --now skips the window and idle checks, never the budget check.
  • At the cap it stops and says so, once, as a skipped row in the digest.

Start low. Six runs a day is already a lot of review.

Tokens are a measure, not the budget

The digest reports how many tokens each project's reviews took, and the run and watch lines show a per-run count. That is there so you can see the cost — it is not what the caps count. Budgets are counted in runs, because a run is the unit you can predict before it happens; tokens you only learn afterward. Claude's figure includes cache reads, which are real tokens the model processed, so it reads larger than a plain input-plus-output count and larger than Codex's for comparable work. A run whose CLI reports no usage simply shows none.