Orchestration Runs

Account status — using account 5

• Window usage so far: 5,236,453 tokens ($4.60) — 169% of its own last observed ceiling
• Total dispatches on this account: 43

Phase Timeline¶

ORCHESTRATOR TOTAL: 0s, 0 tokens, $0.0000 (rows 18)
SHARED TOTAL: 31m, 4,491,455 tokens, $2.5583, 11 row(s) with no token data (rows 1–17)

Total Run Time: 31m (wall clock, 06-10-2026 16:05:08 → 06-10-2026 16:35:58 IST — not a sum of the per-side totals above, since sides overlap)
Total Tokens Consumed: 4,491,455 (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 2,628 · output 19,670 · cache-create 158,110 · cache-read 4,311,047 (96% 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.5583 (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 5

• Window usage so far: 5,315,369 tokens ($4.86) — 172% of its own last observed ceiling
• Total dispatches on this account: 44