PolicyEngine / PolicyEngine/policybench
Supervisor budget meter ignores PRICE_OVERRIDES_PER_1M
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 3
- Avg merge
- 12h 7m
- Merged PRs (30d)
- 13
Description
During the gemini-3.6-flash run (2026-07-21) the supervisor's run_state spent_usd stayed 0.00 for the whole run: Gemini's API returns no cost field and litellm's price map does not cover the id, and the live meter does not fall back to config.PRICE_OVERRIDES_PER_1M the way export-time reconstruction (analysis.model_cost_latency) does. Consequence: the --budget-usd governor cannot bind for any model priced only by override, and projections read $0.
Fix: apply the same override fallback in the supervisor's per-scenario spend accounting that the export path uses.
🤖 Generated with Claude Code
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the supervisor's per-scenario spend accounting and compare it with the export path in analysis.model_cost_latency. Trace how config.PRICE_OVERRIDES_PER_1M is applied when litellm provides no price, then verify that run_state.spent_usd, --budget-usd enforcement, and projections account for override-priced models.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100