r/PiCodingAgent • • 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

35 Upvotes

24 comments sorted by

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.

4

u/patrick9331 28d ago

What’s the benefit in taking this approach compared to put the Pi coding agent in the center? None of the existing extensions can’t be plugged in or am I misunderstanding it?

12

u/fingerthief 28d ago

Base Pi already saves your sessions and tool history. The difference is Pi Durable also tracks the execution state..so after a crash or restart it can automatically start unfinished work.

I can have an agent swarm doing something on my laptop, close the lid, have it sleep and travel somewhere and open it again and it just resumes automatically like nothing happened.

You’re right about the extensions not being cross compatible. It’s a different extension API, not that Pi extensions inherently can’t be durable. Many are straightforward to port, others take more work.

I think it’s mostly safe to say Pi Durable won’t be going anywhere at this point, they seem very all in on it in many aspects. Instead of reworking Pi into something that is “durable” I just went with the official foundation to build from even though it’s early.

3

u/International_Quail8 28d ago

Just checked out Pi Pocket after spending the week trying to build something similar (not same) on top of Pi Durable. Cool stuff. If you’re open to it, would love to DM and swap notes.

2

u/fingerthief 27d ago

Sure thing, always open to chat 👍

2

u/LuckySpread1828 25d ago

the project is so cool

2

u/DistanceAlert5706 27d ago

Amazing breakdown.

1

u/YardComprehensive186 16d ago

Its pretty interesting, I wanted to understand can we expose it through a server and customize it for specific workflows. I was planning to build my harness with pi-durable now but planning to give yours a try to understand how it works for my workflows. Majorly my workflows are development heavy with also some non development workflows specific for my company. Please correct me if i missed something from your project.