Uploaded July 2026 | Updated November 2026, 2 days ago
Most agents today aren't just calling APIs. They're writing and running code, processing files, browsing the web, iterating across multi-step tasks. That means they need more than tools, they need a real workspace: a file system, a shell, installed packages, and state that persists across steps.
But the moment you give an agent execution access, you've introduced a new category of production problem. Model-generated code is untrusted. Local execution doesn't scale. And vanilla containers fall short when you actually need isolation, credential safety, cost controls, and the ability to reproduce what an agent did three sessions ago.
In this session, Amy and Mukil walk through how to give agents their own computer without giving up control:
- The architecture patterns behind production-ready sandboxed execution and when to build your own vs. use a managed sandbox
- What "production-ready" actually requires: secure execution, credential management, resource limits, fast provisioning, snapshots, forks, and persistent state
- How coding agents, data analysis agents, and file-processing workflows behave differently in isolated environments, and what becomes possible when infrastructure stops being the bottleneck
Most agents today aren't just calling APIs. They're writing and running code, processing files, browsing the web, iterating across multi-step tasks. That means they need more than tools, they need a real workspace: a file system, a shell, installed packages, and state that persists across steps.
But the moment you give an agent execution access, you've introduced a new category of production problem. Model-generated code is untrusted. Local execution doesn't scale. And vanilla containers fall short when you actually need isolation, credential safety, cost controls, and the ability to reproduce what an agent did three sessions ago.
In this session, Amy and Mukil walk through how to give agents their own computer without giving up control:
- The architecture patterns behind production-ready sandboxed execution and when to build your own vs. use a managed sandbox
- What "production-ready" actually requires: secure execution, credential management, resource limits, fast provisioning, snapshots, forks, and persistent state
- How coding agents, data analysis agents, and file-processing workflows behave differently in isolated environments, and what becomes possible when infrastructure stops being the bottleneck










