Orchestration Runs

Account status — using account 2

• Window usage so far: 396,959 tokens ($1.12) — 3% of its own last observed ceiling
• Total dispatches on this account: 129

Phase Timeline¶

ORCHESTRATOR TOTAL: 0s, 0 tokens, $0.0000 (rows 10)
SHARED TOTAL: 5m, 1,235,272 tokens, $1.6671, 7 row(s) with no token data (rows 1–9)

Total Run Time: 5m (wall clock, 24-10-2026 17:04:27 → 24-10-2026 17:09:12 IST — not a sum of the per-side totals above, since sides overlap)
Total Tokens Consumed: 1,235,272 (plus 7 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,604 · output 23,702 · cache-create 164,362 · cache-read 1,044,604 (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: $1.6671 (plus 7 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: 483,280 tokens ($1.42) — 4% of its own last observed ceiling
• Total dispatches on this account: 130