Rivet releases Pi 1.0: agents run decoupled from the sandbox
Rivet's Pi 1.0 runs the Pi harness in the backend, separate from the sandbox, so agents keep running when the sandbox crashes or sleeps, aimed at background and multiplayer agents.

Introducing Pi 1.0 for Rivet Running agents inside the sandbox is simple in theory But in production, the sandbox's blast radius becomes your agent's blast radius: 💥 Sandbox OOMs → agent dies 🔑 Credentials → need a proxy 💤 Sandbox asleep → no crons 🔄 Update → redeploy every VM Now with Rivet, you can run the vanilla Pi harness in your backend, separated from the sandbox The sandbox can crash, sleep, or fill its disk. Your agent keeps running Built for background & multiplayer agents