Orchestration Runs

Account status — using account 5

• Window usage so far: 0 tokens ($0.00) — 0% of its own last observed ceiling
• Total dispatches on this account: 66

Phase Timeline¶

ORCHESTRATOR TOTAL: 0s, 0 tokens, $0.0000 (rows 18)
SHARED TOTAL: 40m, 14,243,441 tokens, $8.2438, 11 row(s) with no token data (rows 1–17)

Total Run Time: 40m (wall clock, 12-10-2026 19:16:33 → 12-10-2026 19:56:59 IST — not a sum of the per-side totals above, since sides overlap)
Total Tokens Consumed: 14,243,441 (plus 11 row(s) whose usage was never captured — run execution_tracker.py enrich-audit to backfill. This is a floor, not the total.)
Token breakdown: input 2,695 · output 89,830 · cache-create 408,712 · cache-read 13,742,204 (96% of the total). Cache-read is context a node re-sends to itself across its own tool-use turns, billed at roughly a tenth of fresh input — a large Tokens number that is mostly cache-read is a long tool loop, not a large workload.
Total Cost: $8.2438 (plus 11 row(s) whose usage was never captured — run execution_tracker.py enrich-audit to backfill. This is a floor, not the total.)

Account status — using account 5

• Window usage so far: 81,227 tokens ($0.27) — 1% of its own last observed ceiling
• Total dispatches on this account: 67