Tenfold is built to run multiple Claude Code agents at once, even in the same repository. It keeps track of which agent edits which file, warns you when two collide, and can give each one its own worktree.
Overlap warnings
When two agents edit the same file in the same checkout, both get flagged:
- On the Board, the tile says who else is editing the file.
- In the inspector of the Focus layout, an “Overlapping edits” banner names the file.
- In Code, the overlaps are counted and listed.
Tenfold compares the paths each agent’s edits report. Two agents in separate worktrees work on different paths, so they never collide.
The banner in the inspector has a Move one to a worktree link. It opens the New agent sheet so you can start an agent in its own worktree.
Worktrees
A worktree is a separate folder of the same repository, checked out on its own branch. When Claude Code parallel agents each have a worktree, they can’t overwrite each other’s files.
Start an agent in a worktree
- Press ⌘N in the Workspace.
- Choose the repository.
- Under Where it works, choose New worktree. Press ⌘T to switch between this and Current checkout.
- Name the branch, and pick the branch it starts From.
- Press ⌘↩ to launch.
When another agent already works in that repository, Tenfold marks New worktree as recommended, and the Current checkout card warns that edits may collide. It still starts on the current checkout unless you choose otherwise.
Tenfold creates its worktrees under ~/.tenfold/worktrees/<repo>/<branch>, so they stay out of your project folder.
Bring the work into main
When an agent in a worktree has finished, its tile on the Board offers to bring its branch into main. Tenfold merges the branch into the main checkout’s current branch and keeps its history (a no-fast-forward merge). The worktree stays where it is.
The merge won’t start if the main checkout has uncommitted changes. Commit or stash them first. If the merge hits a conflict, Tenfold aborts it and leaves the main checkout as it was.
Remove a worktree
Tenfold doesn’t remove worktrees, so they stay until you delete them. When you’ve finished with one, run this from your repository:
git worktree list
git worktree remove ~/.tenfold/worktrees/<repo>/<folder>
git branch -d <branch>git worktree list shows the exact path. Git won’t remove a worktree with uncommitted changes, or delete a branch that isn’t merged, so neither command loses your work.
Broadcast
Broadcast sends one prompt to several agents.
- Open the Split layout (⌥⌘2).
- Turn on Broadcast in the control bar. It starts with the sessions in your tiles. Use + add to add more, or remove one from its chip.
- Type the prompt and press ⌘↩ to send it.
Agents sitting at their prompt get it straight away. Busy ones get it queued, and it’s delivered the moment they’re free, so a broadcast never lands in the middle of a turn or answers a permission prompt by accident. Press Esc to close the broadcast bar.
Worktrees you made yourself
Tenfold recognises a session running in any linked git worktree, not only the ones it created. That includes Claude Code worktrees you set up yourself, so the Board can offer to bring their work into main too.