AgentClash

Use case

Evaluate coding agents on real repositories

Coding agents fail on messy repos, flaky tests, and tool limits — not on polished benchmark prompts. AgentClash evaluates patches, test runs, artifacts, and cost on workloads your team actually ships.

live race
gate: pass

Candidate

92correct patch, low cost

Baseline

88stable reference run

Control

73missed edge case

replay timeline

1loaded task inputs and tool policy
2ran sandbox actions and captured artifacts
3scored trajectory and validator evidence
4attached scorecard and release verdict

ci verdict

Candidate clears release gate

Correctness improved, latency within budget, and required artifacts were preserved for review.

agentclash run create --follow

What coding agent eval should check

Built for reviewable agent decisions

Look for correct fixes, sane tool usage, reproducible artifacts, and stable cost/latency — not just a plausible diff in a demo.

Sandboxed real-tool execution

Head-to-head runs with fair constraints

Scorecards for correctness, cost, latency, and tool strategy

Replay trails for every important action

Challenge packs that turn failures into reusable tests

CI gates for baseline versus candidate decisions

Workflow

Coding eval workflow

Package the task

Describe the workload as a challenge pack with inputs, tools, scoring rules, and artifacts.

Race the agents

Run every candidate against the same task with the same constraints.

Replay the evidence

Inspect tool calls, outputs, artifacts, latency, cost, and judge evidence after the run.

Gate the release

Compare candidate and baseline runs, then fail CI before a regression reaches users.

Start with a real bug

Bring your first workload into the loop

Promote a failed coding-agent run into a challenge pack, then race model and harness changes before they reach users.

FAQ

Coding agent evaluation FAQ

Can AgentClash evaluate agents that edit code?

Yes. Challenge packs can run agents in sandboxes with repository fixtures, test commands, and artifact checks for patches and logs.

How do teams compare coding agents fairly?

Run every candidate on the same repo state, tool policy, and time budget, then compare scorecards and replay evidence.

Can coding agent evals run in CI?

Yes. Wire challenge packs into pull request gates so model, prompt, or tool changes cannot merge when correctness regresses.