Marginal cost first
The router prefers workers that cost nothing extra, a subscription CLI you already pay for or a local Ollama model, over pay-per-token APIs. Zero-marginal-cost workers win ties by default.
Admission control, not a monthly surprise
$0.10for run 81cbc07c, design to review, 4 implementers and 1 kept diff
$0.00example cap
CYBERINE_DAILY_USD_CAP=2, off until you set it; a run that would cross it is refused before any adapter startsOne worker or the whole pool
A question gets a single subscription worker. A code task races every available preferred worker at once, because that is where a second opinion is worth paying for.
Refused, not truncated
Once set, the cap is checked before dispatch. A task that cannot fit is declined with the number, rather than half-run and abandoned mid-flight.
Every cent is on disk
Per-run token counts and cost land in run.json with an append-only events.jsonl beside it, indexed across every project.
Run your first race.
Install it, point it at a repo, give it a task.
run 81cbc07cangle: the meterrecorded 2026-09-254 workers3 diffs applied1 kept$0.10 spent