One point of confusion I'm seeing: Lots of people assume you're supposed to run the AI agent harness itself inside a sandbox, and wonder how to do that with Dynamic Workers. The harness does *not* need to be in the sandbox. It can be a regular old Worker (probably a Durable Object, probably using Cloudflare Agents SDK[0]). Remember that an LLM can't manipulate the world at all unless you give it tools. So if you are careful about what tools you give it, it is inherently sandboxed. What we are proposing here is that you basically give the agent two tools: One to explore the APIs it has available to it (returning TypeScript type definitions), and one to execute code against those APIs (input is JavaScript). The latter tool runs the code in a Dynamic Isolate. You can't quite just run Claude Code or Codex in there, since they aren't designed to run in Workers, at least today. But @southpolesteve managed to get OpenCode (a similar harness) running 100% in Workers[1]. It's also not as hard as you might think to write your own harness -- I've done it. That said, if your agent's task specifically involves using a bunch of Linux programs, it may still be best to use containers for that. For instance, if your agent is doing software engineering -- checking out a git repo, running a compiler, etc. -- it may be impractical to make that all work in Workers. Try our Sandbox SDK[2] for that. But if your agent is planning a family vacation, it probably doesn't need to run rustc. It probably just needs to interact with a bunch of APIs. And that's where Dynamic Workers shine. blog.cloudflare.com/dynamic-… [0] developers.cloudflare.com/ag… [1] xitter.cf/southpolesteve/status/… [2] developers.cloudflare.com/sa…