Orchestration Runs

Account status — using account 2

• Window usage so far: 1,632,231 tokens ($2.78) — 13% of its own last observed ceiling
• Total dispatches on this account: 131

Phase Timeline¶

ORCHESTRATOR TOTAL: 10m, 0 tokens, $0.0000 (rows 10)
SHARED TOTAL: 1h 3m, 625,292 tokens, $2.2562, 8 row(s) with no token data (rows 1–11)

Total Run Time: 1h 13m (wall clock, 24-10-2026 17:45:40 → 24-10-2026 18:59:07 IST — not a sum of the per-side totals above, since sides overlap)
Total Tokens Consumed: 625,292 (plus 8 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,601 · output 29,899 · cache-create 115,171 · cache-read 477,621 (76% 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.2562 (plus 8 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 2

• Window usage so far: 1,718,666 tokens ($3.00) — 14% of its own last observed ceiling
• Total dispatches on this account: 132

Account status — using account 2

• Window usage so far: 2,257,523 tokens ($5.04) — 18% of its own last observed ceiling
• Total dispatches on this account: 133