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

How to audit what an agent run actually did with Esf

Check the patch, logs, and cleanup record for a finished run.

Who it is forA security or compliance reviewer asked to confirm what an agent changed and that its sandbox was cleaned up.

The problemA green result does not show which commands ran, what changed, or whether the execution environment was torn down.

The outcomeA written account of the run's patch, gate results, logs, and cleanup status, drawn from the factory's durable records.

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 ./bin/factory describe run RUN_ID to read the manifest, conditions, inventory, and audit trail.
  2. Run ./bin/factory status RUN_ID --watch to see the recorded condition transitions.
  3. Run ./bin/factory logs RUN_ID to read the execution logs. (inferred, check the README)
  4. Run ./bin/factory get changes to find the work item and its spend.
  5. Compare the recorded patch and cleanup outcome against the task and note any gap in a written report.

Prompt for your agent

In the ESF repo at <esf_path>, gather the output of `./bin/factory describe run <RUN_ID>` and `./bin/factory logs <RUN_ID>`. Report the patch, the gate results, and whether cleanup is recorded as verified, and verify that the patch matches the task before concluding.

Caveat. The evidence shows what the factory recorded, so a reviewer still needs to read the patch itself before relying on it.

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