Orchestration Runs

Account status — using account 2

• Window usage so far: 8,704,606 tokens ($9.30) — 46% of its own last observed ceiling
• Total dispatches on this account: 65

Account status — using account 2

• Window usage so far: 8,742,835 tokens ($9.52) — 46% of its own last observed ceiling
• Total dispatches on this account: 66

Phase Timeline¶

ORCHESTRATOR TOTAL: 0s, 0 tokens, $0.0000 (rows 8)
SHARED TOTAL: 2m, 147,297 tokens, $0.6426, 3 row(s) with no token data (rows 1–7)

Total Run Time: 2m (wall clock, 21-09-2026 12:09:53 → 21-09-2026 12:11:42 IST — not a sum of the per-side totals above, since sides overlap)
Total Tokens Consumed: 147,297 (plus 3 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 10,270 · output 3,249 · cache-create 91,072 · cache-read 42,706 (29% 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.6426 (plus 3 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: 8,781,309 tokens ($9.63) — 46% of its own last observed ceiling
• Total dispatches on this account: 67

Account status — using account 2

• Window usage so far: 8,819,620 tokens ($9.74) — 46% of its own last observed ceiling
• Total dispatches on this account: 68