
Bug tracking on a kanban board - BugBoard
Capture bugs with code and triage them on a real-time kanban board.
@s_b_1805 · X
The full gallery
Tech stack
60 projects

Capture bugs with code and triage them on a real-time kanban board.
@s_b_1805 · X

Add a widget to your app that auto-captures screenshots, console logs, and network errors when users report bugs.
@markoradotme · X

BugDetectAI helps developers analyze, understand, and fix code bugs faster using AI.
laxmansubedi · HN
BugDetect AI – AI-powered code debugging assistant

Add a bug report widget in 30 seconds. It captures errors, user journeys and failed API calls — then AI analyzes your code and opens a pull request with the fix.
@syedarhamalii · X

AI-powered code review that runs code in microVMs to catch more bugs.
u/dumbfoundded · Reddit
Ito, AI Code Review that Runs Code I've been using AI code review tools but none of them actually run code so I built one: https://www.ito.ai/ The way it works is that it uses microVMs to spin up your environment with all of the services running. Then a bunch of AI agents go and test the application to collect runtime evidence. The result is you get test cases along with evidence about whether or not the test cases pass or fail. The runtime evidence can be videos, request/response curls, db

Capture UI elements with code context and screenshots to share with AI agents for debugging visual bugs.
Loerei · HN
I found that describing where a broken UI is and taking screenshots for AI agents really sucks. I’m too lazy to explain an indescribable visual bug or capture a millisecond-long flash. I also don’t want to remember which file defines an element, whether it's right in the .tsx or a problem with the Parent Styles in .css. And even if you can point out the exact file, your agent still has to dig through thousands of lines of code to know what on earth you're yapping about. In a 7700-file monorepo like Cal.com, simply giving the right file in the prompt for your agent saves about 68.9% of execution time and 94.2% of the tokens your agent needs to digest. HoverSource gives all the needed information and further pushes it to -88.5% time and -94.5% tokens, basically skipping the entire digging session and jumping straight to reasoning and executing. The save is linear to how big your codebase is. I want to save tokens, but don’t want to spend my time and energy digging manually, and a junio

Professional WordPress bug fixing, 24/7 monitoring, cloud backups, and encrypted credential storage. Request a fix or choose a maintenance plan.
@BugShieldWP · X
🚀 Helping businesses keep their WordPress websites secure, maintained and running smoothly. Feedback is always welcome!

Test your app across devices and browsers to catch bugs automatically in minutes.
@vibe_and_go · X

Capture in-app recordings and screenshots, then triage feedback with AI to fix bugs faster.
@keshav__dev · X
Hi priyanka i am also building in customer feedback space but with some dev related features. Maybe you want to check

Two AI reviewers analyze your code independently and verify each other's bug findings.
@BotariaDotBot · X
This Tuesday I'm launching Botbugger on @ProductHunt 🚀 One AI reviewer gives you 10 "critical" bugs — half hallucinated. So I built two: Claude Code + Codex review your code independently, then cross-check each other. Real bugs with fixes, not noise.

Analyze your codebase to identify where changes introduce risk.
u/jeremyStover · Reddit
My second paying customer bought a full year subscription. I have mentioned https://semfora.ai before, here and there on Reddit. I haven't talked much about what it really provides. I was hoping to drive up some organic traffic, from people that had the motivation to dig past the beta. Stupid idea, but now that we have passed pen tests and hit the minimum requirements check list for security audits, (see other threads about that) we opened up the beta to everyone. Two days after that(

Auto-fix production bugs and get AI code reviews with severity ratings on every PR.
@akshay_nocode · X
Not exactly — Sentry captures errors, BugOps acts on them. It reads the Sentry alert, checks recent commits, traces root cause, and opens a fix PR. Think Sentry as the sensor, BugOps as the on-call engineer that never sleeps.