<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Facundo Taboada</title>
    <description>The latest articles on DEV Community by Facundo Taboada (@ftaboadac).</description>
    <link>https://dev.to/ftaboadac</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3981811%2Fd2ae0bba-d298-40b4-ac6e-60eb575f3e37.jpeg</url>
      <title>DEV Community: Facundo Taboada</title>
      <link>https://dev.to/ftaboadac</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ftaboadac"/>
    <language>en</language>
    <item>
      <title>I got tired of asking coding agents “are you sure?”, so I built a local evidence checker</title>
      <dc:creator>Facundo Taboada</dc:creator>
      <pubDate>Fri, 12 Jun 2026 19:01:19 +0000</pubDate>
      <link>https://dev.to/ftaboadac/i-got-tired-of-asking-coding-agents-are-you-sure-so-i-built-a-local-evidence-checker-11c</link>
      <guid>https://dev.to/ftaboadac/i-got-tired-of-asking-coding-agents-are-you-sure-so-i-built-a-local-evidence-checker-11c</guid>
      <description>&lt;p&gt;I built &lt;a href="https://plumbref.vercel.app/" rel="noopener noreferrer"&gt;Plumbref&lt;/a&gt; because I kept running into the same loop with coding agents&lt;/p&gt;

&lt;p&gt;They would give a confident answer about a repo, and then I’d have to ask:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;“Are you sure?”&lt;/li&gt;
&lt;li&gt;“Did you check the other path?”&lt;/li&gt;
&lt;li&gt;“What about downstream consumers?”&lt;/li&gt;
&lt;li&gt;“Is this actually only used there?”&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The issue wasn’t that the agent couldn’t read code. The issue was that the answer didn’t always come with a clear verification trail&lt;/p&gt;

&lt;p&gt;Plumbref is a local-first MCP server that helps a coding agent check repo answers before giving them back&lt;/p&gt;

&lt;p&gt;It lets the agent:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;break an answer into claims&lt;/li&gt;
&lt;li&gt;search the repository&lt;/li&gt;
&lt;li&gt;read bounded source snippets&lt;/li&gt;
&lt;li&gt;check for contradictions&lt;/li&gt;
&lt;li&gt;classify claims as supported, too_broad, uncertain, contradicted, not_found, or not_verifiable&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Plumbref runs locally:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;no hosted service&lt;/li&gt;
&lt;li&gt;no repo upload&lt;/li&gt;
&lt;li&gt;no database&lt;/li&gt;
&lt;li&gt;no vector store&lt;/li&gt;
&lt;li&gt;no model API key&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Right now it includes an MCP server, a CLI, Markdown/JSON reports, ripgrep-based repo search, bounded snippets, broad-claim detection, and built-in templates for flow explanations, field migrations, change impact, downstream consumers, and external integrations&lt;/p&gt;

&lt;p&gt;It’s still early, but I’ve been dogfooding it on its own repo and I’d like feedback from people using coding agents on real codebases&lt;/p&gt;

&lt;p&gt;Repo: &lt;a href="https://github.com/ftaboadac/plumbref" rel="noopener noreferrer"&gt;https://github.com/ftaboadac/plumbref&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>opensource</category>
      <category>mcp</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
