Orchestration Runs

Account status — using account 5

• Window usage so far: 1,374,429 tokens ($5.18) — 14% of its own last observed ceiling
• Total dispatches on this account: 50

Phase Timeline¶

ORCHESTRATOR TOTAL: 0s, 0 tokens, $0.0000 (rows 18)
SHARED TOTAL: 31m, 12,956,400 tokens, $7.4295, 11 row(s) with no token data (rows 1–17)

Total Run Time: 32m (wall clock, 07-10-2026 15:49:52 → 07-10-2026 16:21:25 IST — not a sum of the per-side totals above, since sides overlap)
Total Tokens Consumed: 12,956,400 (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,682 · output 75,731 · cache-create 367,669 · cache-read 12,510,318 (97% 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: $7.4295 (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: 1,454,243 tokens ($5.46) — 15% of its own last observed ceiling
• Total dispatches on this account: 51