Rivet now supports Pi Durable on Actors
πΉοΈ Multiplayer streaming
πͺΆ Lightweight β ~1.3 MB per agent, starts in ms
πΎ Durable β survives crashes, exactly-once input
π¦ Harness outside the sandbox
π₯§ Vanilla Pi
π± Schedules, JWT, sandboxes & more
- Rivet now supports Pi Durable on Actors πΉοΈ Multiplayer streaming πͺΆ Lightweight β ~1.3 MB per agent, starts in ms πΎ Durable β survives crashes, exactly-once input π¦ Harness outside the sandbox π₯§ Vanilla Pi π± Schedules, JWT, sandboxes & more
Why Pi Durable? Agents in products get interrupted by crashes, restarts, and upgrades. Every step is saved to the Actor's SQLite first, so a run picks up mid-step after a crash. Send the same ππππππππΈπ twice and you get the first result.Tools with Pi Durable are a little different: every tool call is a durable task. Every tool call follows save intent β run β save result. Tools can start multi-step tasks that resume at their last saved phase after a crash, and ππππππ’: "ππππ" marks the ones that canSetup with: ππ({ πππππ, ππππππππ’, πππππππ‘ }) Every agent runs in its own Actor, conversation, and sandbox. Run Pi's coding tools on agentOS, E2B, Daytona, or skip the sandbox for agents that only use your own tools.Run the harness outside the sandbox. The agent loop, keys, and history stay in your backend. The sandbox only sees tool calls, so a crashed or sleeping sandbox never takes the agent down, and no secrets live next to untrusted code.More features: β° Schedules β agents wake themselves on a cron ποΈ Per-agent state β typed documents in the Actor's SQLite π Scoped access β JWTs that reach one Actor π Swappable sandboxes β agentOS, E2B, Daytona π Open source, self-hostable
Wonderful!
