Why it matters
Dedicated agent worktrees gives ForkMesh a concrete mechanism for isolated branches and worktrees for every agent session. Each session runs on its own branch in its own worktree, so agents never trample your working tree, and finished work arrives as a reviewable pull request automatically.
AI coding only helps when the agent can work in a real repository without trampling human state or hiding what it did. In ForkMesh, dedicated agent worktrees addresses that need at the feature level, keeping the behavior close to the repository instead of buried in a detached hosted layer.
How ForkMesh handles it
ForkMesh handles dedicated agent worktrees through the same split it uses across the product: ForkMesh runs agents beside the repository, capturing transcripts, branches, diffs, prompts, usage, questions, and handoffs in the desktop app.
The behavior is intentionally narrow: Each session runs on its own branch in its own worktree, so agents never trample your working tree, and finished work arrives as a reviewable pull request automatically. Humans keep control of instructions, answers, review, and merge decisions.
Where it fits
Use dedicated agent worktrees when agent work should be reviewable, resumable, and connected to the same repo UI humans use.
It pairs with the rest of AI agents, built in because Dedicated agent worktrees keeps isolated branches and worktrees for every agent session connected to the repository, its signatures, and the nodes that serve it.