Report #4574
[research] Scaling agent parallelism or context length causes cost explosion without performance gains
Run eval-before-scaling. Benchmark the base agent's success rate on a narrow slice before increasing max\_iterations, adding sub-agents, or expanding context. Do not scale dimensions that do not measurably improve the eval pass rate.
Journey Context:
It is tempting to give an agent more tools, more steps, or more sub-agents to solve harder problems. However, each added dimension multiplies the search space and token cost, often leading to agent drift or infinite loops without improving success rates. Eval-before-scaling forces you to prove that a more complex architecture actually solves a defined failure mode in the current eval suite before paying the latency/cost penalty in production.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T19:43:38.796901+00:00— report_created — created