<?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: Antonio Trento</title>
    <description>The latest articles on DEV Community by Antonio Trento (@antonio_trento).</description>
    <link>https://dev.to/antonio_trento</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4017853%2F28cfd81d-bd54-41fe-bd76-9ff82dc200b9.jpg</url>
      <title>DEV Community: Antonio Trento</title>
      <link>https://dev.to/antonio_trento</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/antonio_trento"/>
    <language>en</language>
    <item>
      <title>Stop losing your bugs in AI chats: How to connect Cursor/Claude to GitHub Issues</title>
      <dc:creator>Antonio Trento</dc:creator>
      <pubDate>Mon, 06 Jul 2026 13:57:03 +0000</pubDate>
      <link>https://dev.to/antonio_trento/stop-losing-your-bugs-in-ai-chats-how-to-connect-cursorclaude-to-github-issues-43d7</link>
      <guid>https://dev.to/antonio_trento/stop-losing-your-bugs-in-ai-chats-how-to-connect-cursorclaude-to-github-issues-43d7</guid>
      <description>&lt;h3&gt;
  
  
  The Problem with "Vibe Coding"
&lt;/h3&gt;

&lt;p&gt;If you use AI tools like Cursor, Windsurf, or Claude Code, you know the feeling: you are flying through a refactor, the AI is doing great, but suddenly you notice a separate bug. You mention it in the chat, the AI acknowledges it, but you move on. &lt;/p&gt;

&lt;p&gt;Two days later... &lt;em&gt;what was that bug again?&lt;/em&gt; It's buried in a chat history. &lt;/p&gt;

&lt;h3&gt;
  
  
  The Solution
&lt;/h3&gt;

&lt;p&gt;AI agents are great at writing code, but they are isolated from our project management tools. I wanted my AI to just open a GitHub issue for me, just like a real pair programmer would.&lt;/p&gt;

&lt;p&gt;That's why I created &lt;strong&gt;&lt;a href="https://github.com/issuebeam/issuebeam" rel="noopener noreferrer"&gt;issuebeam&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is issuebeam?
&lt;/h3&gt;

&lt;p&gt;It's an open-source (MIT) bridge between your AI agent and your official GitHub repository. It consists of:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;A zero-dependency Python CLI that can list, create, and manage issues.&lt;/li&gt;
&lt;li&gt;Optimized prompt instructions (&lt;code&gt;AGENTS.md&lt;/code&gt;, &lt;code&gt;.cursor/rules&lt;/code&gt;) that teach the AI how to use the CLI.&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Why not just use the &lt;code&gt;gh&lt;/code&gt; CLI?
&lt;/h3&gt;

&lt;p&gt;I wanted this to work everywhere—Windows, Mac, Linux—without forcing developers to install binaries or deal with OS-specific shell scripts. Python is ubiquitous, and by restricting issuebeam to the standard library (&lt;code&gt;urllib&lt;/code&gt;), any AI agent can execute it effortlessly.&lt;/p&gt;

&lt;h3&gt;
  
  
  How to use it in your project
&lt;/h3&gt;

&lt;p&gt;&lt;em&gt;(Insert code blocks showing the quick start)&lt;/em&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Get a GitHub Token&lt;/li&gt;
&lt;li&gt;Run the &lt;code&gt;adopt.py&lt;/code&gt; script in your repo.&lt;/li&gt;
&lt;li&gt;Tell your AI: "Track this bug"&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Conclusion
&lt;/h3&gt;

&lt;p&gt;If you are building software with AI, you need AI-native tooling. issuebeam is completely free and open source. Check out the repository &lt;a href="https://github.com/issuebeam/issuebeam" rel="noopener noreferrer"&gt;here&lt;/a&gt; and let me know your thoughts in the comments!&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>ai</category>
      <category>opensource</category>
      <category>python</category>
    </item>
  </channel>
</rss>
