Stop the agent, keep its disk
An agent works on a customer's project for three weeks. Then the customer pauses their subscription.
On an ephemeral sandbox platform, "pause" means an export pipeline: tar the workspace, push it to object storage, delete the sandbox, and later pull it back and hope the environment reproduces. You wrote that pipeline because keeping a sandbox alive for a paused customer costs money every hour.
On Hoody you stop the container. The filesystem stays as it was: the agent's working tree, its installed tools, its notes to itself in /hoody/databases/. A stopped container uses no CPU and no RAM, and its disk is already inside the server's flat rate. When the customer returns, you start it. Everything is where the agent left it.
No tarball, no bucket, no restore script.
A stopped container is a hard drive with a URL, and the hard drive is included.