Cloud Assumes You Know What a Request Will Cost [Testμ 2026]

At Testμ Conf 2026, Render’s Ojus Save argued that agentic workloads challenge traditional cloud infrastructure assumptions because the true cost, duration, and resource needs of an agent request are not known at admission but emerge as the agent dynamically discovers work through tool calls, retries, branches, and accumulated context. Using two successful executions of the same repository task that produced five and seven graph nodes, he showed that longer runs may reflect appropriate adaptation rather than failure and that node counts can understate costs because later steps carry more context and may repeat expensive verification. Save recommended treating a bounded “run,” rather than an individual request, as the core unit for accounting and control, with token, tool-call, dollar, and wall-clock budgets enforced during execution. He also advised teams to assess run-level distributions such as P95 and P99 rather than averages, separate per-tool timeouts from overall run budgets, explicitly record completion states, use isolated disposable execution environments, and preserve durable workflow and execution state instead of relying on costly, temporary model context. He framed workflows and sandboxes as primitives for managing execution order, recovery, dynamic compute, and secure environments, while noting that durable context and validation approaches remain important design responsibilities for teams.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.