<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Detail</title><link>https://blog.detail.dev/</link><description>Recent content on Detail</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 02 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.detail.dev/index.xml" rel="self" type="application/rss+xml"/><item><title>Towards Self-Driving Codebases</title><link>https://blog.detail.dev/posts/towards-self-driving-codebases/</link><pubDate>Wed, 02 Sep 2026 00:00:00 +0000</pubDate><guid>https://blog.detail.dev/posts/towards-self-driving-codebases/</guid><description>&lt;p&gt;Agents can oneshot games that are actually fun. With the right guardrails, agents can execute incredibly impressive migrations in complex codebases, even rewrites in new languages. But basically all &amp;ldquo;real&amp;rdquo; software work still has human engineers driving the process. How do we get to a place where a much bigger portion of the work gets handled for us, without requiring our attention?&lt;/p&gt;
&lt;p&gt;It seems like agents should be able to build entire software systems themselves. Why is this going so poorly in practice? What new primitives will we need to make it all work? How far can this go?&lt;/p&gt;</description></item><item><title>What kinds of bugs does AI generate?</title><link>https://blog.detail.dev/posts/ai-bug-types/</link><pubDate>Sun, 28 Jun 2026 00:00:00 +0000</pubDate><guid>https://blog.detail.dev/posts/ai-bug-types/</guid><description>&lt;p&gt;What bugs are agents generating? How does vibecoded software break? Where is automated code review coming up short? Is each bug a random oneoff, or can we characterize clear patterns? Are engineers at different companies creating the same few bugs over and over?&lt;/p&gt;
&lt;p&gt;To answer these questions, we took 1,000 example bugs from 99 customer codebases and clustered them.&lt;/p&gt;
&lt;h2 id="same-mistakes-across-codebases"&gt;Same mistakes across codebases&lt;/h2&gt;
&lt;p&gt;We started with 1,000 bugs, each flagged by Detail and subsequently fixed by the customer. We rewrote each bug into a language-agnostic and company-free description of the specific mechanism of the bug, then embedded and clustered those descriptions to group bugs by how they fail.&lt;/p&gt;</description></item><item><title>Detail cleans up your Dead Code</title><link>https://blog.detail.dev/posts/dead-code/</link><pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate><guid>https://blog.detail.dev/posts/dead-code/</guid><description>&lt;p&gt;&lt;strong&gt;tl;dr:&lt;/strong&gt; Detail can now detect dead code in your codebase and open pull requests to remove it. To enable, go to &lt;strong&gt;Dead Code&lt;/strong&gt; in the &lt;a href="https://app.detail.dev/" target="_blank" rel="noopener"&gt;Detail dashboard&lt;/a&gt;
, select a repository, and enable it.&lt;/p&gt;
&lt;p&gt;Every codebase accumulates dead code. Products evolve, features get reworked, a refactor orphans a helper, an experiment gets rolled back and a stray endpoint stays behind. Dead code silently raises the cost of every future change by distracting and confusing the agents that write our software. And agents &lt;em&gt;prolifically&lt;/em&gt; generate it.&lt;/p&gt;</description></item><item><title>Benchmarking a Bug Scanner</title><link>https://blog.detail.dev/posts/bug-scanner/</link><pubDate>Thu, 30 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.detail.dev/posts/bug-scanner/</guid><description>&lt;p&gt;We&amp;rsquo;re all coding with agents now, but delivering high quality software at 10x velocity remains an open problem. Code review bots are an important start, but a lot of bugs are still landing in production. Even top products are accumulating a layer of low-grade brokenness.&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; We need new ways to make products secure and high quality.&lt;/p&gt;
&lt;p&gt;We built a new kind of bug scanner to solve this problem.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The hard part about building a bug scanner is that any meaningfully complicated codebase has many thousands of bugs, and the vast majority don&amp;rsquo;t matter.&lt;/strong&gt; You want to reserve human attention (and your tokens) for the bugs that matter. So, one of the most important ways we benchmark ourselves is that we want the bugs we generate to be significantly more important than the typical finding from a code review bot.&lt;/p&gt;</description></item></channel></rss>