Home / About / Engineering / 070: Every run costed: the platform's own cost and tokens for each scheduled run, on the costs page
Engineering · done
070: Every run costed: the platform's own cost and tokens for each scheduled run, on the costs page
Every run costed: the platform's own cost and tokens for each scheduled run, on the costs page
| Id | 070 |
| Status | done |
| Kind | Story |
| Priority | high |
| Created | 2026-10-16T12:10:00Z |
| Source | the owner, 16 October 2026: "every run that happens should be capturing the cost, the tokens, and everything that happens with it |
| Release | v0.12.74 |
| Effort | small |
| File | admin/engineering/issues/done/070-every-run-costed.md |
Scenario
Given the scheduled runs of the desks and the newsroom
When the accountant reads each run's session usage and final result
Then admin/build/wire-runs.json holds a row per run: when, the task, the cost and the tokens per model, the turns, the subagents, what the permission check refused (by kind, never the command's arguments) and what it published
And the costs page shows the runs by task, by model and one by one, with the working sessions that built the wires counted apart
Outcome
Shipped in v0.12.74: admin/build/runs_ledger.py (adds a run, refuses a row shaped like a key), admin/build/wire-runs.json with the runs of 14 to 16 October, and the runs section of wire/costs.html. Kept current by the accountant (card 071).
For an agent
Issue 070 on newsroom.sgit.ai: Every run costed: the platform's own cost and tokens for each scheduled run, on the costs page. Status done, kind story, priority high, release v0.12.74. Source file admin/engineering/issues/done/070-every-run-costed.md.