Vasek Mlejnsky(@mlejva):What we need is a smart orchestration. Matthew's take is correct. Agents don't always need a full sandbox (which should be a VM, not a container btw), but it's not the agent's job to figure that out. It's the job of the underlying infrastructure. Frankly, given where we're headed, we shouldn't even be thinking in terms of one sandbox per agent. Agents will need their own private clouds. This is one of the problems we're thinking about. If working on this interests you, you should reach out.

2026.09.14 00:10

What we need is a smart orchestration. Matthew's take is correct. Agents don't always need a full sandbox (which should be a VM, not a container btw), but it's not the agent's job to figure that out. It's the job of the underlying infrastructure. Frankly, given where we're headed, we shouldn't even be thinking in terms of one sandbox per agent. Agents will need their own private clouds. This is one of the problems we're thinking about. If working on this interests you, you should reach out.

Fireside Alpha@firesidealpha

2026.09.12 15:52

$NET Matthew Prince reveals running every knowledge worker's agent in containers would need 40x the world's CPUs " Really the whole hyperscale world and all of the mobile world is built on this idea of containers." "The problem with containers is, if you imagine every single knowledge worker on earth has one agent that's running for them, which seems, I mean, pretty conservative, I think most knowledge workers are going more than one agent, and you imagine those agents are all running in containers." "The problem with containers is you have to import a whole operating system and tool chain, all this stuff, just to power that." "Not even looking at GPUs, just looking at CPUs, you need 40x the number of CPUs that are produced in the world in order to just run the agents for those knowledge workers, which is, like, that's not going to work."