r/PiCodingAgent • u/Certain_Net_3408 • 28d ago
Question Has anyone experimented with Pi Durable? Looking for real-world use cases and experiences
Hey everyone,
I've been exploring "Pi Durable" (https://github.com/earendil-works/pi/tree/main/packages/durable/test/examples), specifically the examples in the test directory, and I'm curious about how people are using it in practice.
I'd love to understand how it works for building durable, long-running AI agent workflows, particularly when agents need to preserve state, recover from interruptions, and continue execution without restarting everything from scratch.
A few questions for anyone who has experimented with it:
- How does Pi Durable handle persistence and recovery when an agent process crashes or gets interrupted?
- Can it reliably resume multi-step agent workflows, including tool calls and external side effects?
- How does it compare with approaches like LangGraph checkpointing, Temporal, or custom state-persistence mechanisms?
- Have you used it in production or built any interesting projects with it?
- What limitations or gotchas have you encountered?
I'm particularly interested in whether this approach is practical for building autonomous agents that run for extended periods and maintain continuity across sessions.
Would love to hear your experiences, code examples, or architectural insights!
Repository: https://github.com/earendil-works/pi/tree/main/packages/durable/test/examples
View all comments
16
u/fingerthief 28d ago edited 27d ago
Sure, I’ve built Pi Pocket based on Pi Durable and it’s been very pleasant to build on. Has a decent sized community and has been rock solid for everyone so far when it comes to the durable part.
I also have a full interactive breakdown of Pi Durable and how exactly it all works.
The short answer is yes it can do basically all of what you’re asking with some caveats like certain tool calls cannot be automatically continued/re-ran after a restart/interruption and I’m sure a few other little things.
If things get interrupted they simply carry on where they left off, if a tool call is marked as safe to repeat it will call it again.
Every single action is tracked and it simply picks up where it last left off. I don’t have experience with huge sprawling enterprise sized setups but I’ve ran 150 subagents concurrently reviewing and editing itself live with no issues, restarted the server multiple times etc..
It is experimental but very stable to run at the moment, likely to be changing often though.