Orchestration Runs

Account status — using account 2

• Window usage so far: 3,911,967 tokens ($6.88) — 35% of its own last observed ceiling
• Total dispatches on this account: 43

Phase Timeline¶

ORCHESTRATOR TOTAL: 0s, 0 tokens, $0.0000 (rows 19)
SHARED TOTAL: 36m, 4,164,162 tokens, $3.0545, 12 row(s) with no token data (rows 1–18)

Total Run Time: 36m (wall clock, 01-10-2026 14:48:41 → 01-10-2026 15:24:22 IST — not a sum of the per-side totals above, since sides overlap)
Total Tokens Consumed: 4,164,162 (plus 12 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,616 · output 24,355 · cache-create 224,762 · cache-read 3,912,429 (94% 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: $3.0545 (plus 12 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: 3,992,079 tokens ($7.07) — 36% of its own last observed ceiling
• Total dispatches on this account: 44