<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Git Worktree on Bruce on AI Engineering</title><link>http://www.heyuan110.com/tags/git-worktree/</link><description>Recent content in Git Worktree on Bruce on AI Engineering</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 27 Feb 2026 18:00:00 +0800</lastBuildDate><atom:link href="http://www.heyuan110.com/tags/git-worktree/index.xml" rel="self" type="application/rss+xml"/><item><title>Claude Code Worktree: Run Multiple AI Tasks in Parallel</title><link>http://www.heyuan110.com/posts/ai/2026-02-28-claude-code-worktree-guide/</link><pubDate>Fri, 27 Feb 2026 18:00:00 +0800</pubDate><guid>http://www.heyuan110.com/posts/ai/2026-02-28-claude-code-worktree-guide/</guid><description>&lt;p&gt;&lt;img src="http://www.heyuan110.com/posts/ai/2026-02-28-claude-code-worktree-guide/cover.webp"
 alt="Claude Code worktree mode running multiple parallel AI coding sessions"
 
 loading="lazy"
 decoding="async"
 fetchpriority="low"
 width="1200"
 height="630"
/&gt;
&lt;/p&gt;
&lt;p&gt;You open your terminal. Claude Code is halfway through building a new authentication module. Then Slack pings: there&amp;rsquo;s a production bug that needs fixing now.&lt;/p&gt;
&lt;p&gt;What do you do? Stash your half-finished changes and hope you remember to pop them later? Force-commit a broken state just to switch branches? Tell your team to wait?&lt;/p&gt;
&lt;p&gt;This is the fundamental constraint of single-directory development: &lt;strong&gt;one working directory can only hold one task at a time&lt;/strong&gt;. Switching branches changes your files, but it doesn&amp;rsquo;t give you isolation. If two Claude Code sessions operate on the same directory, they will step on each other&amp;rsquo;s changes.&lt;/p&gt;</description></item><item><title>Claude Code February 2026 Updates: Worktree, Background Agents, Simple Mode</title><link>http://www.heyuan110.com/posts/ai/2026-02-22-claude-code-february-updates/</link><pubDate>Sun, 22 Feb 2026 10:00:00 +0800</pubDate><guid>http://www.heyuan110.com/posts/ai/2026-02-22-claude-code-february-updates/</guid><description>&lt;p&gt;Claude Code released over a dozen versions in February 2026 (v2.1.39 through v2.1.50), introducing several features that fundamentally change how you work. This article covers the most important updates, explains how to use each one, and highlights the practical scenarios where they shine.&lt;/p&gt;
&lt;h2 id="git-worktree-support-the-biggest-workflow-upgrade"&gt;Git Worktree Support: The Biggest Workflow Upgrade&lt;a href="#git-worktree-support-the-biggest-workflow-upgrade" class="anchor" aria-hidden="true"&gt;&lt;svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"
 stroke-linecap="round" stroke-linejoin="round"&gt;
 &lt;path d="M15 7h3a5 5 0 0 1 5 5 5 5 0 0 1-5 5h-3m-6 0H6a5 5 0 0 1-5-5 5 5 0 0 1 5-5h3"&gt;&lt;/path&gt;
 &lt;line x1="8" y1="12" x2="16" y2="12"&gt;&lt;/line&gt;
 &lt;/svg&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;This is the headline feature of February, shipped in v2.1.49. It brings Git&amp;rsquo;s worktree capability directly into Claude Code, making parallel development remarkably simple.&lt;/p&gt;</description></item><item><title>Claude Code Worktree: Run Multiple AI Tasks in One Repo</title><link>http://www.heyuan110.com/posts/ai/2026-02-20-claude-code-worktree/</link><pubDate>Fri, 20 Feb 2026 12:00:00 +0800</pubDate><guid>http://www.heyuan110.com/posts/ai/2026-02-20-claude-code-worktree/</guid><description>&lt;p&gt;Have you ever run into these situations?&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Claude is halfway through a feature when an urgent production bug comes in. You have to &lt;code&gt;git stash&lt;/code&gt; your half-done work or force-commit a messy WIP.&lt;/li&gt;
&lt;li&gt;You want Claude to work on two things at once &amp;ndash; one building a new feature, the other writing tests &amp;ndash; but both sessions edit the same files and create conflicts.&lt;/li&gt;
&lt;li&gt;You want to try a risky refactor but worry about messing up your working directory beyond recovery.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The root cause is simple: &lt;strong&gt;one working directory can only support one in-progress task&lt;/strong&gt;. Switching branches isolates Git history, but the file system is shared. Two Claude sessions operating on the same directory will inevitably step on each other.&lt;/p&gt;</description></item></channel></rss>