4 things worth building with @pidotdev's Pi Durable + @CloudflareDev Durable Objects:
#1 Durable agents for high-stakes workflows
Pi Durable can identify interrupted operations and avoid automatically replaying unsafe calls. Imagine an agent refunding a customer, then crashing tion. You don't want it refunding the customer twice.
Pi Durable checkpoints each step, recording the intent to execute a tool call and whether it completed. After a crash, it knows which operations were interrupted. Unsafe calls aren't blindly retried, so your app can check whether the payment went through before proceeding.
#2 Shared team agents
Pi Durable + Cloudflare Durable Objects are a great foundation for multiplayer agentic coding.
A Durable Object holds the persistent agent state. Multiple clients can connect to the same session, incoming messages are queued or used to steer the agent, and updates are streamed to everyone.
Imagine an agent picking up a GitHub issue and working on a PR while teammates watch or steer the same conversation from their phones, browsers, or terminals. @pidotdev's shared-chat tutorial demonstrates this.
#3 Agents that run anywhere
@badlogicgames built a Pi Durable Android app that runs the agent harness and stores its state locally on his phone, while model calls happen remotely.
Pi Durable separates agent state from execution, with pluggable storage and execution backends. The harness can run anywhere there's a compatible JavaScript runtime, and its tools can execute on another machine. Your durable agent doesn't need an always-running terminal or cloud server just to preserve the agent's state, the harness can run locally, on a phone, or in the cloud.
#4 Build new tools on top of agent state
This is the one we're most excited about.
Pi Durable persists structured tasks, checkpoints, and interrupted operations. That means you can inspect an agent's execution state without asking the model to reconstruct what happened.
We experimented with putting Pi Durable inside a Cloudflare Durable Object and visualizing its stored state without waking the agent.
Imagine using that data to build:
- Debugging dashboards showing exactly where an agent crashed.
- Reliability metrics showing which tool calls repeatedly fail or need recovery.
- Multiplayer dashboards showing pending tasks, who steered an agent, and when.
The interesting part is that durable execution state becomes a new primitive you can build tools on top of, not just something used for crash recovery.
00:00 What is Pi Durable?
07:06 Idea 1: Durability for high-stake workflows
13:16 How to build with Pi Durable
16:31 Durable storage: local vs. cloud
19:46 Pi Durable + Cloudflare Durable Objects
32:20 Idea 2: Multiplayer agents with shared state
35:01 Idea 3: Running the harness on a phone
37:45 Idea 4: Inspecting persistent agent state
🧵👇 Links to YouTube, Apple Podcasts, and Spotify below.
#1 Durable agents for high-stakes workflows
Pi Durable can identify interrupted operations and avoid automatically replaying unsafe calls. Imagine an agent refunding a customer, then crashing tion. You don't want it refunding the customer twice.
Pi Durable checkpoints each step, recording the intent to execute a tool call and whether it completed. After a crash, it knows which operations were interrupted. Unsafe calls aren't blindly retried, so your app can check whether the payment went through before proceeding.
#2 Shared team agents
Pi Durable + Cloudflare Durable Objects are a great foundation for multiplayer agentic coding.
A Durable Object holds the persistent agent state. Multiple clients can connect to the same session, incoming messages are queued or used to steer the agent, and updates are streamed to everyone.
Imagine an agent picking up a GitHub issue and working on a PR while teammates watch or steer the same conversation from their phones, browsers, or terminals. @pidotdev's shared-chat tutorial demonstrates this.
#3 Agents that run anywhere
@badlogicgames built a Pi Durable Android app that runs the agent harness and stores its state locally on his phone, while model calls happen remotely.
Pi Durable separates agent state from execution, with pluggable storage and execution backends. The harness can run anywhere there's a compatible JavaScript runtime, and its tools can execute on another machine. Your durable agent doesn't need an always-running terminal or cloud server just to preserve the agent's state, the harness can run locally, on a phone, or in the cloud.
#4 Build new tools on top of agent state
This is the one we're most excited about.
Pi Durable persists structured tasks, checkpoints, and interrupted operations. That means you can inspect an agent's execution state without asking the model to reconstruct what happened.
We experimented with putting Pi Durable inside a Cloudflare Durable Object and visualizing its stored state without waking the agent.
Imagine using that data to build:
- Debugging dashboards showing exactly where an agent crashed.
- Reliability metrics showing which tool calls repeatedly fail or need recovery.
- Multiplayer dashboards showing pending tasks, who steered an agent, and when.
The interesting part is that durable execution state becomes a new primitive you can build tools on top of, not just something used for crash recovery.
00:00 What is Pi Durable?
07:06 Idea 1: Durability for high-stake workflows
13:16 How to build with Pi Durable
16:31 Durable storage: local vs. cloud
19:46 Pi Durable + Cloudflare Durable Objects
32:20 Idea 2: Multiplayer agents with shared state
35:01 Idea 3: Running the harness on a phone
37:45 Idea 4: Inspecting persistent agent state
🧵👇 Links to YouTube, Apple Podcasts, and Spotify below.
Oct 22, 2026 · 1:17 PM UTC
17
10
132
30,788
Watch on
- YouTube: youtube.com/watch?v=BB84Ez…
- Apple Podcasts: podcasts.apple.com/gb/podcast/pi-…
- Spotify: open.spotify.com/episode/5NcdPN…
Newsletter: superlinear.fm
- YouTube: youtube.com/watch?v=BB84Ez…
- Apple Podcasts: podcasts.apple.com/gb/podcast/pi-…
- Spotify: open.spotify.com/episode/5NcdPN…
Newsletter: superlinear.fm
0
0
10
1,561
@melvindvivas @pidotdev @CloudflareDev Thanks, Melvin! Hope it sparked some ideas for things to build with Pi Durable!
1
0
1
197
@superlinear_fm @pidotdev @CloudflareDev The inspectable execution state is the strongest idea here. I’d be careful calling the harness runnable anywhere, though: tool permissions and side effects still need to be enforced where those tools actually execute.
1
0
2
191
@catmanyauh@pidotdevt@CloudflareDevtable execution state is pretty unique to Pi Durable.
Good point about "runnable everywhere" too. We wanted to say it's easy to deploy across different environments, but you're right that things like tool permissions and side effects still need to be handled wherever the tools execute.
Good point about "runnable everywhere" too. We wanted to say it's easy to deploy across different environments, but you're right that things like tool permissions and side effects still need to be handled wherever the tools execute.
1
0
0
149
@superlinear_fm @pidotdev @CloudflareDev Your refund call still needs an idempotency key at the payment api
1
0
1
289
@deeponailabs @pidotdev @CloudflareDev Yeah you still need that to safely retry the refund, and the good thing about pi durable is that it makes sure an interrupted tool call isn't blindly repeated.
0
0
0
236
@superlinear_fm @pidotdev @CloudflareDev How cool is this! You can co-opt crash-safety to have full malleable software (edit your own source code and then crash yourself and restart).
This is only one of the non-obvious things you can do with Pi Durable that we share in this episode.
x.com/danielgri/stat…
This is only one of the non-obvious things you can do with Pi Durable that we share in this episode.
x.com/danielgri/stat…
@pidotdev-durable is so much fun. The primitives and architecture are so robust and simple to use, extend, and combine.
Built a self-extensible agent harness that can hotswap & hotreload even the server runtime while continuing to build itself.
The core of this is about ~3,000 LOC ions 😅
Almost everything is an extension, following the philosphy of Pi, every part of the UI is.
This has been my toy project for the last 2 weeks, lets see how long it lasts ^^
I started building Ultimate itself at about ~20 commits in, from that point on it evolved while I was using it.
It has self debugging tools built in and conversation branching etc. in a very unique way.
There are so many ideas in there I wanted to always experiment with how it feels, and now I feel like the combo pi-durable and better models, it's possible.
I haven't used it yet for building anything else but the idea behind is that you use it directly in any project you build and the harness eveolves side by side with the project.
Some might ask why? I ask why not? 😅
Here is the repo, just in case anyone wants to get some inspiration: github.com/HazAT/ultimate
This is just beautiful slop, nothing serious
1
0
5
254
@superlinear_fm @pidotdev @CloudflareDev retries are fine right up until the tool call has side effects
2
0
2
35
@superlinear_fm @pidotdev @CloudflareDev the crash between the refund going out and the confirmation coming back is the one case nobody demos, and it's the only one finance ever asks about
0
0
2
19
@superlinear_fm @pidotdev @CloudflareDev I've seen so many people building #1-3, but no one yet who've tried #4!
1
0
2
118
@superlinear_fm @pidotdev @CloudflareDev The refund example is the real test. Checkpoints help, but I'd still want idempotency at the payment API and an explicit unresolved state after a timeout. Let's connect.
0
0
1
18
@superlinear_fm @pidotdev @CloudflareDev The crash between action and confirmation is where it gets scary.
0
0
1
37
@superlinear_fm @pidotdev @CloudflareDev the crash-after-refund case also needs an idempotency key at the payment API. does Pi Durable persist the tool result before moving to the next step?
2
0
0
50


















