Orchestration Runs

Account status — using account 2

• Window usage so far: 14,778,425 tokens ($8.18) — unknown (no real usage-limit rejection observed yet for this account) of its own last observed ceiling
• Total dispatches on this account: 7

Account status — using account 2

• Window usage so far: 14,819,471 tokens ($8.44) — unknown (no real usage-limit rejection observed yet for this account) of its own last observed ceiling
• Total dispatches on this account: 8

Phase Timeline¶

ORCHESTRATOR TOTAL: 0s, 0 tokens, $0.0000 (rows 8)
SHARED TOTAL: 1m, 107,897 tokens, $0.5422, 4 row(s) with no token data (rows 1–7)

Total Run Time: 1m (wall clock, 16-09-2026 18:01:36 → 16-09-2026 18:02:45 IST — not a sum of the per-side totals above, since sides overlap)
Total Tokens Consumed: 107,897 (plus 4 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 5,092 · output 2,980 · cache-create 78,555 · cache-read 21,270 (20% 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.5422 (plus 4 row(s) whose usage was never captured — run execution_tracker.py enrich-audit to backfill. This is a floor, not the total.)