DEDUPEDWho it is forA developer who runs the same model in several coding tools and sees different results from each.
The problemA model's score can reflect the harness it runs in, so a score from one tool may not carry over to another.
The outcomeA clear view of how the same model scores across harnesses and effort levels, which helps decide which tool to use.
What you need first
- A web browser to open the live leaderboard at bughunt.productcompass.pm
- Access to the results/ folder on GitHub or a local copy of the repo for the raw data
Steps
- Open the leaderboard at bughunt.productcompass.pm.
- Find one model in the table, for example DeepSeek V4.1 Flash 1017, and note its Harness and Effort values.
- Compare its Fixed /105 scores across harnesses: DeepSeek Harness, Pi, Claude Code and OpenCode at max effort score 42.7, 42.2, 39.1 and 37.6.
- Check the Effort column to see whether the same harness scores differently at high, low or max effort.
Prompt for your agent
Using the bug-hunt-bench README table, list every row for <model name> with its Harness, Effort, and Fixed /105 score, sorted by score. Output a table. Verify that each row's harness and effort match the source table.
Caveat. Run counts differ across rows, so a difference of one or two points between harnesses may be noise.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for phuryn/bug-hunt-bench and "Compare one model across different coding CLIs"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer