Orchestration Runs

Account status — using account 2

• Window usage so far: 63,302,478 tokens ($56.83) — 331% of its own last observed ceiling
• Total dispatches on this account: 143

Account status — using account 2

• Window usage so far: 63,341,126 tokens ($57.06) — 331% of its own last observed ceiling
• Total dispatches on this account: 144

Account status — using account 2

• Window usage so far: 63,379,752 tokens ($57.16) — 331% of its own last observed ceiling
• Total dispatches on this account: 145

Account status — using account 2

• Window usage so far: 63,498,290 tokens ($57.45) — 332% of its own last observed ceiling
• Total dispatches on this account: 146

Phase Timeline¶

SHARED TOTAL: 18s, 77,182 tokens, $0.2525, 2 row(s) with no token data (rows 1–4)

Total Run Time: 50s (wall clock, 24-09-2026 10:45:00 → 24-09-2026 10:45:50 IST — not a sum of the per-side totals above, since sides overlap)
Total Tokens Consumed: 77,182 (plus 2 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,126 · output 567 · cache-create 35,994 · cache-read 35,495 (46% 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.2525 (plus 2 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: 63,536,824 tokens ($57.48) — 332% of its own last observed ceiling
• Total dispatches on this account: 147

Account status — using account 2

• Window usage so far: 63,654,549 tokens ($57.65) — 333% of its own last observed ceiling
• Total dispatches on this account: 148