Orchestration Runs

Account status — using account 2

• Window usage so far: 96,023,001 tokens ($82.08) — 502% of its own last observed ceiling
• Total dispatches on this account: 198

Account status — using account 2

• Window usage so far: 96,062,451 tokens ($82.31) — 502% of its own last observed ceiling
• Total dispatches on this account: 199

Phase Timeline¶

SHARED TOTAL: 2m, 356,383 tokens, $0.8879, 4 row(s) with no token data (rows 1–11)

Total Run Time: 3m (wall clock, 27-09-2026 03:17:25 → 27-09-2026 03:20:51 IST — not a sum of the per-side totals above, since sides overlap)
Total Tokens Consumed: 356,383 (plus 4 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 7,840 · output 3,032 · cache-create 124,935 · cache-read 220,576 (62% 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.8879 (plus 4 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: 96,340,816 tokens ($82.86) — 504% of its own last observed ceiling
• Total dispatches on this account: 200