Git worktrees let parallel agents share repository context while keeping file edits isolated. Each agent starts from the same base project history, but works in its own directory, branch checkout, file state, and staging area.
The common technical pattern is git worktree isolation. Each worktree has its own directory, branch checkout, file state, and staging area. That allows several agents to work from the same repository history without overwriting each other's files.
Verdent uses this idea through Workspace Isolation. One worker can update tests, another can refactor backend code, and another can adjust UI, with each result kept separate. Sharing context safely does not mean sharing one working tree. It means agents can understand the same project while their execution paths remain reviewable.
