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

How to submit a reviewed run from a manifest with Esf

Apply a checked run.toml file so the same task runs the same way every time.

Who it is forA platform engineer who wants agent runs defined as reviewed files in version control rather than typed by hand.

The problemLong command lines with repo, revision, and task text are easy to get wrong and hard to audit later.

The outcomeA run submitted from a manifest file, with its spend and work items visible in the factory's change list.

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. Write a run.toml file that names the repo, revision, task, agent harness, and verification profile, then commit it for review.
  2. Run ./bin/factory config validate to check the factory configuration the manifest depends on.
  3. Submit it with ./bin/factory apply -f run.toml.
  4. Track the work item with ./bin/factory get changes.
  5. Inspect the finished run with ./bin/factory describe run RUN_ID, which shows the manifest, conditions, inventory, and audit.

Prompt for your agent

In the ESF repo at <esf_path>, read <manifest_path>, confirm it names an allowed repo, a full commit SHA, and a configured agent harness, then run `./bin/factory apply -f <manifest_path>`. Report the resulting run ID and one thing to verify in `./bin/factory describe run <RUN_ID>` before trusting the output.

Caveat. The README does not give the full run.toml schema, so the manifest fields must be taken from the operator guide, not from this card.

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