@vibe_and_go · X

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

@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.

@buildwithahsan · X

Just launched an AI Bug Identifier 🐞 Upload a photo and identify bugs and insects instantly using AI. Building in public and learning every day 🚀 🌐 #AI #BuildInPublic #WebDevelopment

@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.

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

@minmuner_devlog · X

Thanks for the feedback; I’m open to anything.

@yedil_bek · X

Building RedRun - security testing that proves what it finds. Runs the real exploit + hands you the exact request/response: SQLi, IDOR, SSRF, XSS, JWT + AI prompt-injection. Zero false positives. Free scan → Active engine invite-only - DM for access code

@guhanvenkaty · X

Tako's free preview is live: Paste your URL, get a security verdict on your vibe-coded app in 60s. Not an AI wrapper: it fires real requests and PROVES exposure, pulling data from your open DB with no login. Scanning puts you on the early-access waitlist.

@AbdullahYusufY · X

Here is ours We are developing autonomous QA agents feel free to check it out.

@OGVeilScan · X

@CoryMeikleDev · X

I built SiteSay a tool that allows you to embed an incredibly lightweight (4.33kB gzipped) widget to your website for collecting feedback/bug reports with screenshots. It also automatically attaches any uncaught JS errors/unhandled promise rejections.