#313 Jonathan Wall: AI Agents Are Reshaping the Future of Compute Infrastructure

What It Covers

Jonathan Wall, founder of RunLoop AI, explains how AI agents require fundamentally different compute infrastructure than traditional servers. RunLoop provides isolated virtual machine environments (dev boxes) where agents can safely execute unpredictable workloads, access tools, and operate with their own dedicated computing resources, enabling companies to deploy and benchmark thousands of agents simultaneously.

Key Questions Answered

• •Agent Compute Primitives: Agents need isolated virtual machines rather than traditional server infrastructure because they exhibit unpredictable resource usage, write their own code, download documents dynamically, and require access to full computing environments including bash terminals and file systems. RunLoop's dev box provides each agent its own containerized micro-VM with complete tool access while maintaining security boundaries through isolation.
• •Benchmarking for Accuracy: RunLoop's benchmarking system lets developers create domain-specific tests with known starting states and desired outcomes, enabling rapid iteration on agent performance. Companies can test model changes (like switching from one LLM to another), prompt modifications, or framework updates by running agents against consistent benchmarks and measuring score improvements, reducing reinforcement learning cycles from weeks to hours.
• •Agent Deployment Workflow: Developers build agents locally using frameworks like Claude Agent SDK, Langchain DeepAgents, or Codex SDK, then deploy to RunLoop via API. When end users trigger actions (GitHub pull requests, Zendesk tickets, Slack mentions), the system spins up isolated dev boxes, mounts necessary context, executes the agent with full computer access, and tears down the environment upon completion.
• •Enterprise Adoption Pattern: Most effective agent implementations follow an 80-20 model where agents handle the bulk of workflow execution while humans audit and approve final results. This mirrors existing code review patterns where one engineer writes code and another reviews before merging. Companies should start with benchmarking and latest models before considering supervised fine-tuning for high-volume use cases or reinforcement learning for business-critical applications.
• •Workforce Integration Reality: Engineering teams already operate with multiple agents per person, with individual developers choosing different tools (Gemini, Claude, custom agents) based on personal workflow preferences and specific tasks. Rather than top-down corporate mandates, agent adoption follows individual experimentation patterns where coworkers with similar roles use different agents in different ways, similar to how people have distinct research and writing processes.