Coding agent can create huge code diffs. Someone still has to read it. seendiff is a local diff tool for large changes. Track what you've seen, review in chunks, and pull the coding agent in to explain its own work.
1. Go through the painful review process, or 2. Go YOLO mode and commit without reviews.
If you care about maintenance of your codebase you will want to go through the pains review your code.
Most code diff tools today were built for the past world - but AI scale of code is different.
So I built seendiff - to scratch my own itch. It: 1. Automatically keeps track of what code you've seen in a diff 2. Keeps track of manually reviewed code blocks. 3. Integrates a code walkthrough that lets your AI walk you through the code 4. Other nifty features that matter - local global search, minimap etc.
seen-state is the right primitive imo @abhishek_iyer . the thing i keep wanting next to it is why-state, becuase a hunk i skimmed for two seconds and one i actually reasoned about both end up marked seen, and on a 900 line agent diff those arent the same risk at allll.
I often loose track of what I already reviewed and what’s pending, so I get where that pain comes from :))
the "what you've seen in a diff" tracking is the part that'd actually get me to use this daily. is that state local to the machine/clone, or does it sync somewhere if I review on my laptop and then pull the same branch on a different machine later
Love that seendiff pulls the coding agent in to explain its own diffs, turning review from a chore into a guided walkthrough of large AI generated changes.
About seendiff on Product Hunt
“Code diff viewer with progress tracking”
seendiff launched on Product Hunt on August 29th, 2026 and earned 135 upvotes and 7 comments, placing #4 on the daily leaderboard. Coding agent can create huge code diffs. Someone still has to read it. seendiff is a local diff tool for large changes. Track what you've seen, review in chunks, and pull the coding agent in to explain its own work.
seendiff was featured in Open Source (68.8k followers), Software Engineering (42.9k followers) and GitHub (41.4k followers) on Product Hunt. Together, these topics include over 50.3k products, making this a competitive space to launch in.
Who hunted seendiff?
seendiff was hunted by fmerian. 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.
Want to see how seendiff stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
fmerian
Hey Product Hunt 👋
AI code is difficult to review.
So you have two options:
1. Go through the painful review process, or
2. Go YOLO mode and commit without reviews.
If you care about maintenance of your codebase you will want to go through the pains review your code.
Most code diff tools today were built for the past world - but AI scale of code is different.
So I built seendiff - to scratch my own itch. It:
1. Automatically keeps track of what code you've seen in a diff
2. Keeps track of manually reviewed code blocks.
3. Integrates a code walkthrough that lets your AI walk you through the code
4. Other nifty features that matter - local global search, minimap etc.
Im putting it up at https://seendiff.com in case its useful to someone else.
Free. Open source.
What does your agentic code review process look like?