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

How to turn a coding task into a verified patch with Esf

Run a coding agent in an isolated microVM and get a patch plus gate results.

Credentials. Agent and Cube credentials must be narrowly scoped and stored locally, since factory.toml and .env are not meant for Git.

Who it is forA developer or engineering lead with a repo and a clear change to make, who wants an agent to do the work without touching their workstation.

The problemLetting a coding agent edit a working tree directly risks unverified changes, leaked credentials, and no record of what happened.

The outcomeA durable patch, logs, and manifest for one task, with the agent output checked by the configured verification gates.

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. Run git clone https://github.com/mitkox/esf.git and cd esf, then mkdir -p bin and make build.
  2. Run ./bin/factory init, then edit factory.toml with your Cube API endpoint, template, proxy address, agent harness, and verification profile. Keep factory.toml and .env out of Git.
  3. For local Temporal, copy deployments/dev/temporal/.env.example to deployments/dev/temporal/.env, set a random database password, then run make temporal-up.
  4. Run ./bin/factory config validate and ./bin/factory doctor, then start the worker with ./bin/factory worker in one terminal.
  5. In another terminal run ./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, then check it with ./bin/factory status RUN_ID and ./bin/factory logs RUN_ID. (inferred, check the README)

Prompt for your agent

In the ESF repo at <esf_path>, submit a run against <repo_url> at commit <full_sha> with the task in <task_file>, then poll `./bin/factory status <RUN_ID>` until it finishes. Report the patch location and gate results, and confirm the verification gates passed before calling the run successful.

Caveat. ESF produces changes for review and does not decide what ships, and the default verification profile expects repository-owned build.sh and test.sh scripts.

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