Workflow ·
Five Agents, Five Branches, One Repo. Nobody Steps on Anybody.
TRMNLY gives each agent its own git worktree, and Fleet lets a pool of them work your task board while you decide what lands.

Put two coding agents in one checkout and they end up editing each other's files. Git already has the fix. A worktree is a second checkout of the same repository, so you can have more than one branch checked out at a time.1 TRMNLY builds its parallel-agent workflow on that.
A worktree per agent
In TRMNLY, a worktree belongs to a project. It shares the project's .git folder but has its own folder on disk.2 New Worktree… (⌃⌘N) runs git worktree add and copies over the untracked files you name, like .env or node_modules, so the new checkout works without a fresh install.2
The agent follows whichever worktree is active. File writes, git_*, bash and the project's tools all run in that worktree's folder, not the main one.2 Agents can manage worktrees themselves with seven worktree_* tools.2
Claude Code has its own worktree tool. TRMNLY installs a trmnly-worktrees skill telling it to use TRMNLY's tools instead, so the checkout gets registered with the project, and to adopt any worktree it made by hand.3
Fleet works the board
Fleet takes this further. You say how many workers to run (up to eight) and how much they may spend, then press Start. Each worker claims a ready card from the project's kanban board, does the work in its own worktree, gets its branch reviewed, and lands it.4,5
"Ready" means not finished, not claimed, and not waiting on another card. When an agent claims a card, other agents are told who has it and keep off.4,6 If a worker crashes, its claim runs out and the card goes back in the queue.4 The board is the queue, so anything that can write to it can feed the fleet, Claude Code over MCP included.4
Workers use an installed Claude Code, Codex or Gemini CLI first, so a long run comes out of a subscription you already pay for. Approvals and the audit log still apply.4
What lands is up to you
The default is Open a PR: push the branch, open a pull request, and park the card for you to merge. Merge when green and Merge immediately are opt-in for each project, and you can't set them over MCP.4 The reviewer can't edit code. If its verdict is missing or makes no sense, that counts as a rejection, and the card goes back on the board with the findings attached.4
Cleaning up
Each worktree's git menu has Merge PR & Clean Up…, and agents have worktree_merge_cleanup. Both merge the PR and remove the worktree.2 Removing a worktree deletes its folder, so push anything uncommitted first.2
Sometimes you want several tries at the same task, not several tasks. race_start gives one prompt to two to five agents, each in its own worktree. race_pick keeps the branch you like and removes the rest, but never a worktree with uncommitted changes.4,7
Sources
- 1.Git documentation, "git-worktree: Manage multiple working trees." git-scm.com
- 2.TRMNLY docs, "Worktrees." trmnly.dev/docs/worktrees
- 3.TRMNLY changelog, 0.1.76, "Worktrees, and Claude Code knows to use them" (September 4, 2026).
- 4.TRMNLY docs, "Fleet." trmnly.dev/docs/fleet
- 5.TRMNLY changelog, 0.1.47, "Fleet: agents that work your task board on their own" (August 6, 2026).
- 6.TRMNLY changelog, 0.1.88, "An agent that claims a card keeps other agents off it" (September 19, 2026).
- 7.TRMNLY changelog, 0.1.89, "Race several agents on one prompt and keep the best answer" (September 19, 2026).