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 before it gets confirmation. 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.

Introducing 𝚍𝚞𝚛𝚊𝚋𝚕𝚎-𝚑𝚊𝚛𝚗𝚎𝚜𝚜. Run Pi, OpenCode, Codex, Claude Code, eve, fx, or your own harness durably on Vercel. With 𝚍𝚞𝚛𝚊𝚋𝚕𝚎-𝚑𝚊𝚛𝚗𝚎𝚜𝚜, agents automatically resume work after failures and run for hours, days, or months. vercel.com/blog/making-every…

i had opus 5.5 distill this 30 min lecture about pi-durable into a 7 min vid with my voice. > qwen3 tts could do a better job cloning my voice > the video looks great. i'm working on industrializing these kind of explanation videos. good starting point, but i still recommend watching the full lecture for a more detailed explainer.

radius.earendil.com Radius gives you inference, built for Pi. Radius speaks the pi-messages protocol. Why does that matter? 👇🏼

I tried every harness under the sun and always circle back to @pidotdev. Many offer good features, but it's all or nothing. I can’t cherry-pick what I like. It is less effort to customize Pi, then spend time circumventing workflows that don’t fully match my needs.

@pidotdev doing big things.