Orchestration Runs

Account status — using account 2

• Window usage so far: 26,281,290 tokens ($26.98) — 137% of its own last observed ceiling
• Total dispatches on this account: 115

Account status — using account 2

• Window usage so far: 26,320,235 tokens ($27.12) — 138% of its own last observed ceiling
• Total dispatches on this account: 116

Phase Timeline¶

SHARED TOTAL: 3m, 797,104 tokens, $0.9748, 3 row(s) with no token data (rows 1–5)

Total Run Time: 3m (wall clock, 22-09-2026 00:20:50 → 22-09-2026 00:24:03 IST — not a sum of the per-side totals above, since sides overlap)
Total Tokens Consumed: 797,104 (plus 3 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 5,593 · output 7,588 · cache-create 106,485 · cache-read 677,438 (85% 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: $0.9748 (plus 3 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: 27,078,394 tokens ($27.95) — 142% of its own last observed ceiling
• Total dispatches on this account: 117

Account status — using account 2

• Window usage so far: 27,117,230 tokens ($28.06) — 142% of its own last observed ceiling
• Total dispatches on this account: 118

Account status — using account 2

• Window usage so far: 27,156,047 tokens ($28.09) — 142% of its own last observed ceiling
• Total dispatches on this account: 119