<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>claude</title><description/><link>https://kevinquillen.com</link><language>en</language><item><title>Auryn: A Unified View of Your AI Coding Sessions</title><link>https://kevinquillen.com/auryn-unified-view-your-ai-coding-sessions</link><guid isPermaLink="false">403 at https://kevinquillen.com</guid><description>
&lt;span property=&quot;schema:name&quot;&gt;Auryn: A Unified View of Your AI Coding Sessions&lt;/span&gt;

            &lt;div property=&quot;schema:text&quot; class=&quot;text-content clearfix field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;Over the last year, AI coding assistants have become a regular part of my development workflow. Like many developers, I have spent countless hours working with tools such as Claude Code, OpenAI Codex CLI, Gemini CLI, and GitHub Copilot CLI. These tools have become incredibly capable partners for everything from debugging difficult issues to planning new features, exploring unfamiliar codebases, reviewing architecture decisions, and generating documentation.&lt;/p&gt;&lt;p&gt;As these tools became more deeply integrated into my day-to-day work, I started noticing a new problem.&lt;/p&gt;&lt;/div&gt;
      
&lt;span rel=&quot;schema:author&quot;&gt;&lt;span lang about=&quot;https://kevinquillen.com/user/1&quot; typeof=&quot;schema:Person&quot; property=&quot;schema:name&quot; datatype&gt;Kevin&lt;/span&gt;&lt;/span&gt;

&lt;span property=&quot;schema:dateCreated&quot; content=&quot;2026-06-22T14:29:14+00:00&quot;&gt;&lt;time datetime=&quot;2026-06-22T10:29:14-04:00&quot; title=&quot;Monday, June 22, 2026 - 10:29&quot;&gt;June 22nd, 2026&lt;/time&gt;
&lt;/span&gt;
</description><pubDate>Mon, 22 Jun 2026 14:29:14 GMT</pubDate><dc:creator>Kevin</dc:creator></item></channel></rss>