Who it is forA developer building regression tasks or RL environments from real agent work who needs each task to be independently checked before use.
The problemA transcript is not a task. It needs a repo base, reference patch, verifier, and a Docker run that rejects the base and accepts the reference.
The outcomeA bundle with a recorded Docker validation run that moves from generated to verified, or a clear rejection with reasons.
What you need first
- Existing Claude Code or Codex session history on the local machine
- Git, and Node.js 22.19+ or 24+ for the DeepSeek Harness app
- A model provider configured in Harness Settings for review, hardening, calibration, and evolution
- Docker, only when building or validating executable environments
Steps
- Install and launch Evo Trace with
curl -LsSf https://raw.githubusercontent.com/jinzijian/EvoTrace/main/install.sh | shand thenevotrace. - Configure a model provider in Harness Settings, and make sure Docker is running.
- Run
/review 1to run the sequential four-agent review on candidate 1. - Run
/build 1to compile an execution candidate, then/validate 1to run two-state Docker validation. - Run
/runsto inspect the saved validation evidence and check the status.
Prompt for your agent
Using the EvoTrace repo at https://github.com/jinzijian/EvoTrace, run /review 1, /build 1, and /validate 1 in the DeepSeek Harness app for the candidate <candidate-number>. Report the asset status and the Docker validation result from /runs. Verify that the asset is marked Verified only if the base was rejected and the reference was accepted.
Caveat. Generated tasks and verifiers stay candidates until they pass the documented evidence and Docker validation gates, and Docker is required for this path.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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