Three themes dominated AI tooling this week: infrastructure finally catching up to agent runtime requirements, open-weight models closing the gap on specialized security tasks, and the slow death of the human-in-the-loop bottleneck for provisioning. None of these are incremental—each one removes a category of workaround that engineers have been quietly maintaining for months.
Durable Objects Stay Alive During Outbound Connections
Cloudflare's Durable Objects used to evict after 70–140 seconds of CPU inactivity, which created a brutal mismatch with LLM token streaming: your object could get torn down mid-response. The standard workaround was a heartbeat loop or periodic ping to keep the runtime warm—real code that existed for no reason except to fight the platform.
As of June 19, Durable Objects now stay alive for the full duration of any active outbound connection, with a 15-minute ceiling per connection. No code changes required. If you have a Durable Object managing a WebSocket to an LLM or an agent maintaining a TCP session to an external service, it will not be evicted while that connection is open.
This matters because the heartbeat pattern wasn't just annoying—it was a concurrency footgun. Ping logic racing against eviction introduced timing-dependent failures that were hard to reproduce and harder to debug. The behavioral change is automatic and deployed.
