This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Ockham
Stops coding agents from leaving copies of a bug behind
Ockham is an open-source Claude Code plugin that keeps a coding agent's changes small and checked. When a session starts, it lists what the project already has. When an edit replaces a line that another file also has, it says where the other copy is. When the task ends, it checks what was written. In its benchmark, agents with no tool fixed the second copy of a bug in 1 session of 25; with Ockham's end-of-task checks, in 15 of 15. MIT, in development.
Hi Product Hunt, I'm Antonio. I built Ockham after watching coding agents fix the line a ticket names and leave the same bug in another file.
A prompt can ask an agent to keep a change small. It can't see what the project already has at the moment the agent writes, and it can't check what was written. Ockham adds those two things to Claude Code:
When the session starts: a short set of rules, plus the helpers the project's files already share.
When an edit replaces a line that another file also has: the file and the line of the other copy.
When the task ends: it compares what changed and stops the agent once if it finds a new dependency, a second version of an existing helper, a copy left unfixed, a check that was dropped, or risky logic with no test.
Nothing ships before the benchmark says it helps: 44 tasks, headless sessions, checks the agent never sees. The README has the numbers, including where it loses. A session costs more than with no tool, mostly because of the tests Ockham asks for (OCKHAM_TESTS=off leaves that rule out).
It is not finished: phases 0 to 3 of 9 are done and phase 4 is built. It runs in Claude Code today; Codex is still open.
Install (Claude Code, Node.js 20+):
claude plugin marketplace add Octonove/ockham
claude plugin install ockham@ockham
Tell me where it gets in your way: a warning that was wrong, a check that should exist, a task it makes worse.
About Ockham on Product Hunt
“Stops coding agents from leaving copies of a bug behind”
Ockham was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #151 on the daily leaderboard. Ockham is an open-source Claude Code plugin that keeps a coding agent's changes small and checked. When a session starts, it lists what the project already has. When an edit replaces a line that another file also has, it says where the other copy is. When the task ends, it checks what was written. In its benchmark, agents with no tool fixed the second copy of a bug in 1 session of 25; with Ockham's end-of-task checks, in 15 of 15. MIT, in development.
On the analytics side, Ockham competes within Open Source, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how Ockham performed against the three products that launched closest to it on the same day.
Who hunted Ockham?
Ockham was hunted by Antonio J Bergoños. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Ockham including community comment highlights and product details, visit the product overview.
Hi Product Hunt, I'm Antonio. I built Ockham after watching coding agents fix the line a ticket names and leave the same bug in another file.
A prompt can ask an agent to keep a change small. It can't see what the project already has at the moment the agent writes, and it can't check what was written. Ockham adds those two things to Claude Code:
When the session starts: a short set of rules, plus the helpers the project's files already share.
When an edit replaces a line that another file also has: the file and the line of the other copy.
When the task ends: it compares what changed and stops the agent once if it finds a new dependency, a second version of an existing helper, a copy left unfixed, a check that was dropped, or risky logic with no test.
Nothing ships before the benchmark says it helps: 44 tasks, headless sessions, checks the agent never sees. The README has the numbers, including where it loses. A session costs more than with no tool, mostly because of the tests Ockham asks for (OCKHAM_TESTS=off leaves that rule out).
It is not finished: phases 0 to 3 of 9 are done and phase 4 is built. It runs in Claude Code today; Codex is still open.
Install (Claude Code, Node.js 20+):
claude plugin marketplace add Octonove/ockham
claude plugin install ockham@ockham
Tell me where it gets in your way: a warning that was wrong, a check that should exist, a task it makes worse.