Orchestration Runs

Account status — using account 5

• Window usage so far: 14,243,441 tokens ($8.24) — 124% of its own last observed ceiling
• Total dispatches on this account: 68

Phase Timeline¶

ORCHESTRATOR TOTAL: 0s, 0 tokens, $0.0000 (rows 18)
SHARED TOTAL: 42m, 14,069,750 tokens, $7.5445, 11 row(s) with no token data (rows 1–17)

Total Run Time: 42m (wall clock, 13-10-2026 16:09:40 → 13-10-2026 16:52:09 IST — not a sum of the per-side totals above, since sides overlap)
Total Tokens Consumed: 14,069,750 (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,699 · output 89,088 · cache-create 326,535 · cache-read 13,651,428 (97% 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: $7.5445 (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: 14,324,915 tokens ($8.52) — 125% of its own last observed ceiling
• Total dispatches on this account: 69

Account status — using account 5

• Window usage so far: 28,313,191 tokens ($15.79) — 246% of its own last observed ceiling
• Total dispatches on this account: 70