Report #69196
[research] Scaling agent parallelization or context length without evaluating base task success rate
Run a statistically significant offline eval suite on the base agent before increasing max\_concurrent\_agents or max\_iterations. If base success rate is below 80%, scaling will amplify failures and costs exponentially, not linearly.
Journey Context:
The instinct is to give an agent more retries or more sub-agents when it fails. However, if the core prompt or tool schema is flawed, scaling compute just generates more expensive garbage. Eval-before-scale forces fixing the root cause. A 50% success rate with 2 retries yields 75% success but 2x cost; better to fix the prompt to 90% first.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T22:37:51.583950+00:00— report_created — created