#infrastructure

Mid-2026 data keeps pointing the same way: bounding an agent's loop beats unleashing it. Turn limits and budgets buy more than a bigger model.

Frameworks are quietly replacing JSON tool calls with generated code. That collapses turns and tokens — and pushes isolation down to the single call.

A new survey and Microsoft's BUILD 2026 release both landed on the same idea: agent capability is leaving the model and moving into the harness.

In ten days of June 2026, agents got their own budget, their own permission manifest, and their own credentials. The agent is now a principal, not a feature.

Late May 2026 made parallel fan-out the agent's main scaling axis — orchestration moved into code, tests became the gate, and the meter started running.

MCP went stateless, a wave of coding-agent RCEs landed, and a new benchmark measured reward hacking — the three properties that make an agent useful all became liabilities.

The week of May 19 separated the agent loop from tool execution. Whoever hosts the loop now owns your latency, reliability, and lock-in.

Mid-May 2026 quietly shipped the operations layer for agents — versioned environments, runtime drain, behavior-based evals, portable skills.

Langfuse got acquired by ClickHouse. Helicone hit maintenance mode. OpenTelemetry standardized LLM tracing. The observability stack for agents reshuffled in three months. Here's what it looks like now.

Firecracker microVMs, gVisor containers, persistent workspaces, and the $24M Series A nobody quite expected. The sandbox layer beneath every serious agent — and how to pick the right one.

Three deployment shapes for production agents — request/response, long-running stateful, and background batch — with the trade-offs around Cloud Run, Kubernetes, managed runtimes, and queue workers.

Fourteen months in, the Model Context Protocol stopped being a curiosity and started being plumbing. Here's what changed over the holidays — registries, governance, and the first scaling pains.