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

How to build a new agent harness and score it with Doc2 Harness

Use the builder image and your own model key to generate a harness, then score it.

Credentials. The build needs a local LiteLLM gateway holding your own API key, so keep that key out of shared logs and committed files.

Who it is forA researcher or developer who wants to see how a chosen model builds a coding agent harness from a development document and a skeleton.

The problemMeasuring a model on building a full harness, not just writing a patch, requires a repeatable build pipeline and a separate evaluation stage.

The outcomeA built harness in your output directory, scored against the 94-scenario catalog with per-scenario receipts.

What you need first

  • Python 3.11 or newer
  • Docker installed and running
  • The repo cloned locally
  • For building a new harness only: the builder image, a local LiteLLM gateway, and your own API key

Steps

  1. Run docker pull ghcr.io/yuyaoge/doc2harness-builder:latest.
  2. Set up a local LiteLLM gateway holding your API key, following src/stage1/README.md.
  3. Run PYTHONPATH=src python3 src/stage1/run_build.py --builder-tag <your-builder-tag> --dry-run to print the orchestration plan without starting anything. (inferred, check the README)
  4. Run PYTHONPATH=src python3 src/stage1/run_build.py --builder-tag <your-builder-tag> --out-dir results/ for the real build, which the README says takes about 15 minutes. (inferred, check the README)
  5. Run the scoring command from the score-existing-agent-harness use case against results/ /agent.

Prompt for your agent

Use the repo YuyaoGe/doc2harness to build a new harness with the builder tag <builder-tag> and output to <output-dir>, using the local LiteLLM gateway at <gateway-url>. Run the dry-run first, then the real build, and report the output path. Verify the dry-run printed the full plan before starting the real build.

Caveat. The README's build command is truncated in the source, so the exact builder-tag value format should be checked in src/stage1/README.md before running.

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