# AI use cases for Durable Pi (disler/durable-pi) Repo: [disler/durable-pi](https://github.com/disler/durable-pi) | Use cases: 4 | Page: https://dedupedai.com/use-cases/disler-durable-pi/ Durable Pi is a set of tools for running persistent AI agents on your own machines, with a web hub, a terminal client and a curl-friendly HTTP API. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Run a durable agent on your own machine: https://dedupedai.com/use-cases/disler-durable-pi/run-durable-agent-on-own-machine/ - Watch a proactive agent open an incident: https://dedupedai.com/use-cases/disler-durable-pi/watch-proactive-agent-open-incident/ - Attach a terminal to a running agent and steer it: https://dedupedai.com/use-cases/disler-durable-pi/attach-terminal-and-steer-agent/ - Gate a release check behind your own approval: https://dedupedai.com/use-cases/disler-durable-pi/gate-release-check-with-approval/ ## How to run a durable agent on your own machine with Durable Pi Repo: [disler/durable-pi](https://github.com/disler/durable-pi) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Start a device server and web hub so an agent keeps running after you close the browser. **Who it is for:** A developer who wants a long-running AI agent on a laptop or server that survives closing the browser or restarting the terminal. **The problem:** Chat sessions tied to one window stop when the window closes, and resume does not restore which tool call was running. **The outcome:** A local device server on port 4780 and a web UI on http://localhost:4781 that show one durable agent you can reopen at any time. ### Steps 1. Run `cp .env.example .env`, then set OPENROUTER_API_KEY in .env. 2. Run `cp dpi-network.example.yaml dpi-network.yaml`. 3. Run `just install`, then `just net up local`. 4. Run `just hub build`. 5. In one terminal run `just backend run`. In a second terminal run `just hub start`. 6. Open http://localhost:4781 in a browser and start a session on the local device. ### Prompt to paste into your agent ```text In the Durable Pi repo at , follow the Manual Install steps in the README up to starting the hub on http://localhost:4781. Report the URL that responds and the names of the device and session shown in the web UI. Verify that the device appears as local in the network tree. ``` ### Caveat The README says remote devices need passwordless ssh and that exe.dev VMs need an exe.dev account, so start with the local device only. Risk, credentials: The setup writes a bearer token to ~/.dpi/backend.env and copies the OpenRouter key into each device's backend.env, so keep those files private. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/disler-durable-pi/run-durable-agent-on-own-machine/ ## How to watch a proactive agent open an incident with Durable Pi Repo: [disler/durable-pi](https://github.com/disler/durable-pi) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Run the demo where an agent starts on its own, investigates a failing checkout and waits for your deploy approval. **Who it is for:** An engineer evaluating proactive AI agents who needs to see how an agent reacts to a production log signal before trusting one with real work. **The problem:** It is hard to judge a proactive agent from a description alone, and a deploy step needs a human decision. **The outcome:** A running demo at the printed URL in which the agent asks to deploy at about 30 seconds and waits for your decision. ### Steps 1. Run `just proactive install`. 2. Run `just proactive build`. 3. Run `just proactive take` and open the URL it prints. 4. Wait for the agent to ask to deploy, then decline, question or approve the deploy in the web UI. 5. Run `just proactive stop` when finished. ### Prompt to paste into your agent ```text In the Durable Pi repo at , run `just proactive take` and capture the printed URL. Report the URL and whether the agent asked to deploy within about 30 seconds. Verify that the deploy task is waiting for approval and has not run. ``` ### Caveat The demo uses a mock production log stream, and the README gives per-row and per-incident costs for the Jev and agent models, so check costs against your OpenRouter account before running it repeatedly. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/disler-durable-pi/watch-proactive-agent-open-incident/ ## How to attach a terminal to a running agent and steer it with Durable Pi Repo: [disler/durable-pi](https://github.com/disler/durable-pi) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Reconnect from the terminal to an agent on a device and send it follow-ups or interrupts. **Who it is for:** A developer who prefers the terminal and wants to check on or redirect an agent that is already working on a device. **The problem:** Closing a terminal normally loses the working context, and the agent should not stop when the client does. **The outcome:** A terminal view of the agent where you can send, steer, queue or interrupt work, and where the agent keeps running after you exit. ### Steps 1. Make sure the device server is running with `just backend run`. 2. Run `just tui attach local` to open the local device. 3. Press Enter to send or steer, Alt+Enter to queue a follow-up, and Esc to interrupt. 4. Press Ctrl+C on an empty prompt to exit, then run `just tui attach` again to reattach. ### Prompt to paste into your agent ```text In the Durable Pi repo at , run `just tui attach local` against a running device server. Report the session and agent names shown. Verify that after Ctrl+C the agent is still running by reattaching and seeing its latest transcript. ``` ### Caveat The terminal client needs a registered device, so complete the local setup first with `just net up local`. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/disler-durable-pi/attach-terminal-and-steer-agent/ ## How to gate a release check behind your own approval with Durable Pi Repo: [disler/durable-pi](https://github.com/disler/durable-pi) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Run the release-check durable job so the agent gathers evidence and waits for you before it publishes. **Who it is for:** A release owner who wants an agent to prepare release evidence while a person makes the final publish decision. **The problem:** Automated release steps can publish before anyone reviews the evidence, and a restart can repeat side effects. **The outcome:** A release-check job that pauses at its approval phase, with the evidence gathered by a subagent, and publishes only after you approve. ### Steps 1. Start the hub with `just hub start` and open http://localhost:4781. 2. Select the device and session you want to run the job in. 3. Open the Tasks tab and run the release-check durable job. 4. Review the evidence the subagent gathered, then approve or stop the job at its waiting phase. ### Prompt to paste into your agent ```text In the Durable Pi repo at , open the web hub, run the release-check durable job from the Tasks tab, and report the phase it stops at. Verify that it waits for approval before any publish step runs. ``` ### Caveat The README names release-check as an example job, so confirm what its publish phase does in your own setup before relying on it for real releases. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/disler-durable-pi/gate-release-check-with-approval/