Decouple the brain from the hands

agents. So theme one is decoupling the brain from the hands. Um so when we first set out to build Managed Agents, we started with the container. We put the harness in the sandbox in the same container. Now the problem here is, what happens if the harness dies or the container dies? What we saw is you actually lose the session. So basically, this architecture is kind of tricky for long horizon agents because what can happen is your agent's running, and And container dies, you lose everything with it. Also, as models get more capable, putting the credentials in the same container with the agent itself can be problematic. So, for example, giving Claude access to a bunch of your secrets and letting it run for 10 hours and not watching it can be a little bit spooky and have some security concerns, especially as models get extremely capable. So, for this reason, we kind of decouple what we call the brain, that's the harness, from the hands, the execution environments, and manage agents to set up like this. So, the story here is that the harness becomes a stateless process that talks to a session. The session is an append-only event log and that can reach out to hands, which are just containers. So, that's just Those are sandboxes where work is done. And one thing that's interesting is Claude is increasingly capable of managing many hands. So, that is you can give one harness access to many different containers to perform to execution. And Claude can manage this very easily and and and and effectively. If the session, uh sorry, if the harness dies or sandbox dies, it's completely fine because the session is always backed up in this append-only log and credentials are never actually added to the sandbox. They're stored in a separate vault. So, this decoupling actually makes it quite reliable and safe, particularly for long-horizon tasks. And this is kind of one of the core ideas that underpins manage agents architecturally.