Copies and worktrees
Copy or worktree
A copy
A full folder that stands on its own. It brings your .env files and node_modules along, and leaves build output and caches behind. On a Mac, copies share disk space with the original; on Windows and Linux they are usually full copies.
A Git worktree
A linked worktree on a new branch from the current commit, sharing the repository’s history. Uncommitted files stay behind, and ignored ones come along only when you tick them under Options.
Make them
Right-click the project in the sidebar and choose Duplicate for copies, or New worktree for Git worktrees.
Press + for as many as you need, up to 50. Each one gets a random tag in its name; type over it to name the copy for its job.
Give each one something to run if you like: an action, a shell command, or an agent prompt. Use the same task for all of them, or one each.
Create them. They appear under the original in the sidebar, each with the original's services and actions, ready to start.
One prompt, several attempts
To try one prompt several ways, write it, open the menu next to Send and pick Run in duplicates. It runs 2 to 10 times: in the current terminal and in new copies of the project, one agent per copy.
Good to know
- Options for copies: keep committed work only, pull the latest changes, reinstall Node dependencies, or group the copies into a sidebar folder.
- Copies run the same commands as the original, so give each one its own port, for example through a PORT variable. lpm flags a clash before starting, but it doesn't isolate ports or containers.
- Copies and worktrees share the original's session memory, so an agent in one can pick up where another left off.
- Deleting a copy removes its folder. Deleting a worktree also deletes its branch, so push anything you want to keep.
- From a terminal or an agent,
lpm duplicateandlpm worktreemake 1 to 50 at once. - SSH projects can't be duplicated.
Read more: running Claude Code in parallel, worktrees for AI agents and copies compared with worktrees.