<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Parallel-Agents on Tokenise</title><link>https://tokenise.rosvetic.com/tags/parallel-agents/</link><description>Recent content in Parallel-Agents on Tokenise</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 02 Oct 2026 07:00:00 +0000</lastBuildDate><atom:link href="https://tokenise.rosvetic.com/tags/parallel-agents/index.xml" rel="self" type="application/rss+xml"/><item><title>Run parallel Claude Code sessions without them stepping on each other</title><link>https://tokenise.rosvetic.com/posts/claude-code-worktrees-parallel-sessions/</link><pubDate>Fri, 02 Oct 2026 07:00:00 +0000</pubDate><guid>https://tokenise.rosvetic.com/posts/claude-code-worktrees-parallel-sessions/</guid><description>&lt;p&gt;Two Claude Code sessions in the same checkout will eventually edit the same file. Git worktrees are the standard answer: each session gets its own working directory and branch, backed by the same repository history. Claude Code has a flag for it, and the &lt;a href="https://code.claude.com/docs/en/worktrees" target="_blank" rel="noopener noreferrer"&gt;worktree docs&lt;/a&gt;&#10; cover more edge cases than the one-liner suggests.&lt;/p&gt;</description></item></channel></rss>