DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to gate a release check behind your own approval with Durable Pi

Run the release-check durable job so the agent gathers evidence and waits for you before it publishes.

Who it is forA release owner who wants an agent to prepare release evidence while a person makes the final publish decision.

The problemAutomated release steps can publish before anyone reviews the evidence, and a restart can repeat side effects.

The outcomeA release-check job that pauses at its approval phase, with the evidence gathered by a subagent, and publishes only after you approve.

What you need first

  • Node.js 24
  • just
  • zsh
  • An OpenRouter API key for OPENROUTER_API_KEY in .env
  • For remote devices: passwordless ssh, and an exe.dev account for exe.dev VMs

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 for your agent

In the Durable Pi repo at <repo path>, 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.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page