harness-evals
v0.2.16
Published
Agent-first coding-agent evaluation harness with Docker isolation, skills onboarding, and result reporting.
Maintainers
Readme
harness-evals
Reusable coding-agent evaluation harness for running real agent CLIs in isolated Docker workspaces.
Recommended setup
Start by installing the packaged skill from the npm package:
npx skills add harness-evals --skill harness-evalsThen open your coding agent and ask it to use the skill, for example:
can you setup evals for this project?The skill guides the agent to:
- check whether the
harness-evalsCLI is installed - ask whether to install the CLI globally or locally in the project when it is missing
- inspect the project structure, package manager, test commands, Docker usage, CI, and existing agent config
- ask what you want to test and how before creating cases
- optionally derive cases from existing sessions, failures, or repeated workflows
- map your goals to eval cases, agents, mocks, assertions, scoring, and reports
- create or update
harness-evals.yamland goal-specific eval files - run
harness-evals listand a focused first validation run
After setup
After your agent creates harness-evals.yaml and the first goal-specific cases, use the CLI loop directly. If the CLI is installed locally, use your package runner such as npx harness-evals, pnpm exec harness-evals, or bunx harness-evals.
harness-evals list
harness-evals run --case <case-id> --agents <agent-name>
harness-evals view --latest --openFor controlled comparisons, declare a root-level benchmarks entry, then run
and inspect its exact case/arm/trial matrix:
harness-evals list --benchmark <id>
harness-evals run --benchmark <id>
harness-evals view --benchmark <id>
harness-evals view --benchmark allBenchmark objectives (one primary plus an optional secondary) and quality gates are independent from the weighted
scoring summary. Reports preserve every trial, reduce trials within each
case, and compare candidate values with the declared baseline.
harness-evals runs coding agents in Docker. If docker.image is set, that ready image is used directly. Otherwise the harness builds and reuses a local managed image from the selected adapters' installation recipes.
Refresh a managed image when upstream packages or the Docker base image changed but the install manifest did not:
harness-evals run --refresh-managed-image --case <case-id> --agents <agent-name>Documentation
Start with the bundled docs hub at skills/harness-evals/docs/index.md, or jump to the installation and configuration guide and CLI reference.
Contributor architecture notes live under docs/design/index.md.
