Orchestration Runs

Account status — using account 5

• Window usage so far: 21,072,522 tokens ($17.99) — 213% of its own last observed ceiling
• Total dispatches on this account: 54

Phase Timeline¶

ORCHESTRATOR TOTAL: 0s, 0 tokens, $0.0000 (rows 18)
SHARED TOTAL: 37m, 8,863,883 tokens, $6.4965, 11 row(s) with no token data (rows 1–17)

Total Run Time: 38m (wall clock, 08-10-2026 15:47:11 → 08-10-2026 16:25:23 IST — not a sum of the per-side totals above, since sides overlap)
Total Tokens Consumed: 8,863,883 (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,645 · output 88,547 · cache-create 385,617 · cache-read 8,387,074 (95% 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: $6.4965 (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: 21,151,512 tokens ($18.26) — 214% of its own last observed ceiling
• Total dispatches on this account: 55

Account status — using account 5

• Window usage so far: 29,936,405 tokens ($24.49) — 303% of its own last observed ceiling
• Total dispatches on this account: 56