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

How to pause agent runs for human approval with Esf

Stop each run after gates report, then approve, reject, or rework it.

Who it is forA reviewer or maintainer who must sign off on agent-written code before it moves forward.

The problemAgent success alone does not show a change is correct, so each result needs a deliberate decision before it advances.

The outcomeEach run waits at a review step, and a rejected change can be reworked as a child run with a note explaining the fix.

What you need first

  • Go 1.27.2 and Node.js 26.12.0 for v0.6.2 development
  • Git
  • An existing CubeSandbox deployment with a READY template
  • A Temporal service, or the included local Temporal Docker Compose stack
  • Narrowly scoped credentials configured locally, kept out of Git
  • Repository-owned build.sh and test.sh scripts, or other gates set for your project

Steps

  1. Set [review] enabled = true in factory.toml, then run ./bin/factory config validate.
  2. Submit a task with ./bin/factory run --repo https://github.com/your-org/your-repo --rev FULL_COMMIT_SHA --task "Describe the change and acceptance criteria" --agent opencode2 --verification default. (inferred, check the README)
  3. After the gates report, inspect the run with ./bin/factory describe run RUN_ID.
  4. Approve with ./bin/factory review RUN_ID --approve, or reject with ./bin/factory review RUN_ID --reject --note "use the formal greeting".
  5. For rework after a rejection, run ./bin/factory run --change CHANGE_ID --parent-run RUN_ID ... with the same task and repo settings.

Prompt for your agent

In the ESF repo at <esf_path>, check run <RUN_ID> with `./bin/factory describe run <RUN_ID>` and list its gate results and the patch it produced. Report whether the run is waiting for review and what the reviewer should check before approving, and do not approve it yourself.

Caveat. The review pause only applies when [review] enabled is set to true, and the README does not describe who is authorized to approve.

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