Orchestration Runs

Account status — using account 1

• Window usage so far: 14,346,065 tokens ($20.43) — 326% of its own last observed ceiling
• Total dispatches on this account: 134

Account status — using account 1

• Window usage so far: 14,385,329 tokens ($20.57) — 327% of its own last observed ceiling
• Total dispatches on this account: 135

Phase Timeline¶

ORCHESTRATOR TOTAL: 3m, 0 tokens, $0.0000 (rows 8–25)
SHARED TOTAL: 20m, 3,459,217 tokens, $2.4100, 11 row(s) with no token data (rows 1–24)

Total Run Time: 24m (wall clock, 06-10-2026 14:51:58 → 06-10-2026 15:16:16 IST — not a sum of the per-side totals above, since sides overlap)
Total Tokens Consumed: 3,459,217 (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 17,729 · output 18,736 · cache-create 182,605 · cache-read 3,240,147 (94% 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: $2.4100 (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 1

• Window usage so far: 14,463,407 tokens ($20.72) — 328% of its own last observed ceiling
• Total dispatches on this account: 136

Account status — using account 1

• Window usage so far: 14,501,566 tokens ($20.83) — 329% of its own last observed ceiling
• Total dispatches on this account: 137

Account status — using account 2

• Window usage so far: 21,426,764 tokens ($17.42) — 228% of its own last observed ceiling
• Total dispatches on this account: 66

Account status — using account 2

• Window usage so far: 22,227,741 tokens ($17.95) — 236% of its own last observed ceiling
• Total dispatches on this account: 67