Dan Robinson

We built a bug finder. We're finding serious, "let's fix that right now" issues in every codebase we run it on. Introducing Detail!

Pretty crazy that there's a wiki page for Software Factory and it has nothing to do with AI. Originally written in 2005.

We migrated from Graphite to @Aviator_co_ and you should consider doing the same. We love: - Much better merge queue. 5 mins for a 20 PR stack vs 1.5 hours on Graphite. This is killer when you're merging code at agent volumes. - Configs live in git, agent friendly to iterate on. - CLI is agent-friendly. The skill we use for managing stacked diffs is 3x shorter. - Snappier web UI, in the rare occasion when I need to look at it. Can't wait to see Origin but until then we'll be on Aviator.

@jessethanley @nate_yiu @greptile @cursor_ai We are detail.dev, @detaildotdev on here.

Yah good question. PRs get @greptile'd. Everything is @cursor_ai bug bot'd. Weekly deep reviews from Detail dot dev (@danlovesproofs what is the handle? Fix your marketing!) Monthly deep deep deep reviews by Detail. Majority of code I write with agents is at my desk. I only use frontier models (5.5 mostly). Strictly use @cursor_ai and @opencode for quick stuff. I read over everything and test locally if it touches something critical.

Commit milestone yay.

twelve alien spacecraft arrive around the world; the military assembles a team led by an expert linguist to attempt to make contact.

@BentoumiTech @danlovesproofs Detail is the best poorly marketed product in the AI tool space.

If you want to run this on your own codebase, check out Detail. The biggest difference vs Ramp's scan pipeline is that Detail has an additional feedback loop: we track which vulns get fixed, and we use that data to prioritize better going forward. So when you scan your code with Detail, we're making use of fix / no-fix decisions from across our customer base. In fact, we don't even look for vulns in particular – just high-value bugs. But if you find many bugs and optimize for which ones get fixed, you'll organically find a lot of vulns, because when a vuln comes in that is bad (and real) engs jump all over it. You can think of this as the bitter lesson coming for security scanners. Don't write a scanner that looks for SQL injections, write a scanner that looks for bugs and do a good job picking the bugs that engs are going to fix, and you'll end up finding the SQL injections.

@BenjaminHouy @detaildotdev 🙏🙏🙏

AI should help you ship better code. That's why I love @detaildotdev so much. You connect it to GitHub and it surfaces bugs you missed. And the bugs it finds are genuine.

@0x15f @detaildotdev unbothered. moisturized. happy. in his lane. focused. flourishing. 258 bugs lighter.

I would definitely recommend using @detaildotdev. I think we started using the tool in December 2025 and these are the stats

@sachiniyergreen @tankots get this man on a billboard, he has become wispr's strongest soldier.

you may not like it but this is what peak performance looks like

@BenjaminHouy @detaildotdev Send feature requests anytime!

Really impressed with @detaildotdev. Connected it to GitHub, received an email with a list of bugs a few hours later. All real bugs. One critical. Will make my overwhelmed indie hacker life much easier.

The hard part about building a bug finder is that every codebase has thousands of bugs, and the vast majority do not matter. Human attention is the bottlenecking resource in building software right now, so the right goal is: how do we pick out the 1% of bugs that are important, and put those ones in front of engineers? Fun post here about how we used a chess tournament to determine that the bugs we're finding are several sigmas more important than the typical CR bot comment.

@KeiraArts @jessethanley @MostlyTechPod @IanLandsman @aarondfrancis Amazing! Send feedback & feature requests anytime, DM or myfirstname at product domain.

@jessethanley @MostlyTechPod @IanLandsman @aarondfrancis Tried it by your recommendation, it found some amazing edge cases. Really good!

everyone should install @detaildotdev today it basically runs a cron to hack you every month (and hack all your recent commits). strong recommend.

I'll update the site! The backstory, if you were curious: - We built a bug finder and optimized around finding bugs that were confidently worth an engineer's attention. - One of the main signals we use for whether a bug is worth an engineer's attention is: if we put a bug in front of an engineer, will they fix it? (We track this and optimize against it.) - Security vulns perform very well here. So, organically, Detail started finding a lot of vulns. We aren't security researchers by background. We aren't building SAST or managing your supply chain. We're trying to find bugs you'll care about, and low-hanging vulns are a category of bugs that you'll probably care a lot about. We stumbled into this use case, and we're figuring out how to serve it better. In some sense, this is bitter lesson in action: don't build a security scanner, instead build a codebase defect scanner and optimize for what engineers judge to be worth fixing, and in practice you'll find a lot of the vulns that matter as part of doing that. But we find other high value issues too: data loss bugs, billing mistakes, etc.

@jessethanley @MostlyTechPod @aarondfrancis Nothing about directly checking for vulnerabilities of any kind. Just 'bugs'.

We have spent over £30k on annual pen tests over the last 3yrs. They found things, but nothing major. In the last months, detail.dev has uncovered nearly 10 complex high-sev auth/idor vulns on our endpoints. Less than $500 bucks.

@chadwhitacre @_m27e It's satisfying to watch, which matches the feeling we want our product to give you: the "ahhhh that's better" that people get from powerwash / weedwacking / deepclean videos. Except for your codebase.

Rejected billboard slogans for Detail.

@danlovesproofs Not gonna lie, it's not bad