Git worktree lets one repository have multiple working trees. A linked worktree can give an urgent fix its own directory while unfinished files remain in the original checkout. It is not a separate backup: linked worktrees share repository data, while their working files and index are separate.

First run git status in the existing checkout and note what is modified or untracked. Choose a new directory and a suitable branch for the second task. The worktree manual normally prevents checking out a branch that is already checked out elsewhere; use a separate branch instead of overriding that protection casually.

After adding the worktree, check git worktree list and run git status inside the new directory before editing. Keep terminal paths obvious so a commit or build happens in the intended checkout. Remember that a second directory does not isolate shared branches and repository administration from other worktrees.

Before cleanup, inspect status and preserve any work you need, including untracked files. Prefer git worktree remove for a clean linked tree rather than deleting its directory manually; avoid force-removal as a routine shortcut. Removable-drive worktrees may need the documented lock feature. This guide performs no deletion and recommends no history rewriting.