<?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: Eddie San Juan</title>
    <description>The latest articles on DEV Community by Eddie San Juan (@eddiesanjuan).</description>
    <link>https://dev.to/eddiesanjuan</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%2F3777787%2Fd5048fe9-caac-4e30-9250-658b73da8878.png</url>
      <title>DEV Community: Eddie San Juan</title>
      <link>https://dev.to/eddiesanjuan</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/eddiesanjuan"/>
    <language>en</language>
    <item>
      <title>I built an open-source tool that records screen + voice bug reports producing AI-ready markdown</title>
      <dc:creator>Eddie San Juan</dc:creator>
      <pubDate>Tue, 17 Feb 2026 14:24:49 +0000</pubDate>
      <link>https://dev.to/eddiesanjuan/i-built-an-open-source-tool-that-records-screen-voice-bug-reports-producing-ai-ready-markdown-3mmo</link>
      <guid>https://dev.to/eddiesanjuan/i-built-an-open-source-tool-that-records-screen-voice-bug-reports-producing-ai-ready-markdown-3mmo</guid>
      <description>&lt;p&gt;I kept running into the same problem in AI-assisted dev workflows: bug reporting was still manual and slow.&lt;/p&gt;

&lt;p&gt;You find an issue, then switch to writing mode — describe context, take screenshots, organize everything, and rewrite it for your coding agent.&lt;/p&gt;

&lt;p&gt;So I built markupR.&lt;/p&gt;

&lt;p&gt;It takes screen + voice and turns it into structured markdown with inline screenshots that AI tools can use directly.&lt;/p&gt;

&lt;p&gt;Workflow&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Record your screen while narrating what’s wrong&lt;/li&gt;
&lt;li&gt;Transcription + timestamp analysis&lt;/li&gt;
&lt;li&gt;Frame extraction at relevant moments&lt;/li&gt;
&lt;li&gt;Output: AI-ready markdown report&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Why I’m building it this way&lt;/p&gt;

&lt;p&gt;• Open source (MIT)&lt;br&gt;
• Free forever core workflow&lt;br&gt;
• BYOK if you want cloud models&lt;br&gt;
• Local options if you don’t&lt;/p&gt;

&lt;p&gt;I’m not trying to build lock-in here — I want a tool people actually use and improve over time.&lt;/p&gt;

&lt;p&gt;If you try it, I’d love feedback on:&lt;/p&gt;

&lt;p&gt;• where your current bug-report handoff breaks&lt;br&gt;
• whether this output format is useful in real projects&lt;br&gt;
• what would make this production-worthy for teams&lt;/p&gt;

&lt;p&gt;Repo + demo: &lt;a href="https://github.com/eddiesanjuan/markupr" rel="noopener noreferrer"&gt;Github&lt;/a&gt;&lt;br&gt;
(If useful, I can also share architecture details and implementation notes.)&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>ai</category>
      <category>programming</category>
      <category>testing</category>
    </item>
  </channel>
</rss>
