<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>adimension - jujutsu</title>
    <subtitle>Adam Bosnjakovic&#x27;s personal site</subtitle>
    <link rel="self" type="application/atom+xml" href="https://adimension.io/tags/jujutsu/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://adimension.io"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2026-06-30T00:00:00+00:00</updated>
    <id>https://adimension.io/tags/jujutsu/atom.xml</id>
    <entry xml:lang="en">
        <title>Worktrees, GitButler, Jujutsu: finding a version control model for parallel AI agents</title>
        <published>2026-06-30T00:00:00+00:00</published>
        <updated>2026-06-30T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Adam Bosnjakovic
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://adimension.io/blog/worktrees-gitbutler-jujutsu/"/>
        <id>https://adimension.io/blog/worktrees-gitbutler-jujutsu/</id>
        
        <summary type="html">&lt;p&gt;I run AI coding agents in parallel. Several at once, on the same repo,
each chewing on a different change while I review, test and steer. It&#x27;s
a genuinely different workflow from one-human-one-branch, and it broke
my git habits fast.&lt;&#x2F;p&gt;
&lt;p&gt;The core need isn&#x27;t just &quot;isolate some throwaway branches.&quot; It&#x27;s this: I
want several long-lived lines of change that I keep working on and
testing at the same time, I want to deal with conflicts &lt;em&gt;there and then&lt;&#x2F;em&gt;
rather than discovering them at some upstream merge weeks later, and I
want rebasing to be seamless rather than a chore I dread. I went through
three tools chasing that. This is what happened with each.&lt;&#x2F;p&gt;</summary>
        
    </entry>
</feed>
