Share work in a Project worktree

Keep several branches of one repository available in a managed Project without moving the conversation to another Project.

What a shared worktree is

Worktrees in a managed Project are shared by everyone with access to the Project. Their branches are named elowen/<label>-<suffix>.

They separate work but they are not security-isolated, and they do not select the execution target for a conversation.

Create or remove one

1. Ask Chetty to list the existing worktrees with the Project tool's worktrees action.
2. Ask it to create one with worktree_create.
3. Before removing one with worktree_remove, preserve uncommitted files and commits that are not already reachable from another branch.

For isolated repository work, create native Git worktrees instead; read Work in a separate Git worktree.

Check that it worked

worktrees lists the new worktree with its branch and state, and the Project's Environments page manages the shared worktrees of its environment.

Related guides

Work in a separate Git worktree, Projects overview, Environments overview, Start, stop and snapshot an environment.