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: 59

Phase Timeline¶

ORCHESTRATOR TOTAL: 0s, 0 tokens, $0.0000 (rows 18)
SHARED TOTAL: 46m, 11,256,036 tokens, $7.5106, 11 row(s) with no token data (rows 1–17)

Total Run Time: 47m (wall clock, 10-10-2026 16:16:17 → 10-10-2026 17:03:00 IST — not a sum of the per-side totals above, since sides overlap)
Total Tokens Consumed: 11,256,036 (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,672 · output 86,777 · cache-create 308,387 · cache-read 10,858,200 (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: $7.5106 (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: 80,861 tokens ($0.28) — 0% of its own last observed ceiling
• Total dispatches on this account: 60

Account status — using account 5

• Window usage so far: 11,256,036 tokens ($7.51) — 37% of its own last observed ceiling
• Total dispatches on this account: 61