<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>intentic blog</title>
        <link>https://intentic.dev/blog/</link>
        <description>What we have worked out about running a fleet of coding agents, and what we got wrong on the way.</description>
        <language>en-us</language>
        <atom:link href="https://intentic.dev/blog/rss.xml" rel="self" type="application/rss+xml" />
        <item>
            <title>One worktree per agent, and why the count stops mattering</title>
            <link>https://intentic.dev/blog/one-worktree-per-agent/</link>
            <guid isPermaLink="true">https://intentic.dev/blog/one-worktree-per-agent/</guid>
            <pubDate>Fri, 04 Sep 2026 00:00:00 GMT</pubDate>
            <description>Running several coding agents at once fails on shared state long before it fails on model quality. A git worktree each is the boundary that fixes it.</description>
        </item>
    </channel>
</rss>
