<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Coding Agents on Will Velida</title>
    <link>https://www.willvelida.com/tags/coding-agents/</link>
    <description>Recent content in Coding Agents on Will Velida</description>
    <generator>Hugo -- 0.140.2</generator>
    <language>en</language>
    <lastBuildDate>Sun, 09 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.willvelida.com/tags/coding-agents/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Running parallel GitHub Copilot agent sessions with tmux and git worktrees</title>
      <link>https://www.willvelida.com/posts/running-parallel-github-copilot-sessions-tmux-git-worktress/</link>
      <pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.willvelida.com/posts/running-parallel-github-copilot-sessions-tmux-git-worktress/</guid>
      <description>&lt;p&gt;When I first started using GitHub Copilot, I kept to the chat window, as I wasn&amp;rsquo;t too comfortable with the idea of using the CLI for long prompts. The chat interface in VS Code was more friendly and intuitive for me, and I felt more in control using the chat UI.&lt;/p&gt;
&lt;p&gt;Over time, I&amp;rsquo;ve been using GitHub Copilot CLI more often. As the scope of work increases (and as demand from stakeholders also increases!), I&amp;rsquo;ve found myself firing up multiple terminals to do multiple different tasks on a project. However, I&amp;rsquo;ve had to be careful about how I&amp;rsquo;ve done that, as I didn&amp;rsquo;t want to have to deal with the trouble of merge conflicts only made worse by overzealous coding agents!&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
