<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Worktree on Yushi's Blog</title><link>https://blog.yushi91.com/blog/worktree/</link><description>Recent content in Worktree on Yushi's Blog</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright © 2025, Yushi Cui.</copyright><lastBuildDate>Tue, 12 May 2026 10:00:00 +1200</lastBuildDate><atom:link href="https://blog.yushi91.com/blog/worktree/index.xml" rel="self" type="application/rss+xml"/><item><title>Git Worktree: The Feature I Knew About but Never Tried Until I Had To</title><link>https://blog.yushi91.com/blog/git-worktree-parallel-agents/</link><pubDate>Mon, 11 May 2026 10:00:00 +1200</pubDate><guid>https://blog.yushi91.com/blog/git-worktree-parallel-agents/</guid><description>&lt;p&gt;&lt;img src="https://blog.yushi91.com/images/git-worktree-parallel-agents.webp" alt="Git worktree for parallel agent work" loading="lazy"&gt;
&lt;/p&gt;
&lt;h2 id="the-feature-i-kept-ignoring"&gt;The feature I kept ignoring&lt;/h2&gt;
&lt;p&gt;I&amp;rsquo;d &lt;a href="https://blog.yushi91.com/blog/git-worktrees-parallel-development-ai/"&gt;written about git worktree before&lt;/a&gt;, and I&amp;rsquo;d heard it come up in discussions about parallel workflows plenty of times. Every time I nodded and thought &amp;ldquo;that sounds useful&amp;rdquo; and then went back to my single-branch life.&lt;/p&gt;
&lt;p&gt;My normal workflow was simple: one branch, one agent, one task at a time. Sometimes I&amp;rsquo;d open a second agent for a code review or quick QA check, but that was it. The most I ever pushed it was three agents at once: one implementing, one doing research with Gemini, and one handling frontend. Even then, they barely touched the same files, and the work was still mostly sequential.&lt;/p&gt;</description></item></channel></rss>