Work in a separate Git worktree

A Git worktree is another checkout of the same repository, usually on a separate branch. It keeps work on a feature apart from the checkout you already use, but it is not a new security boundary: files remain subject to the same Project access.

Create a worktree

1. In a terminal inside the repository, create a branch and checkout, for example: git worktree add ../feature-work -b feature-branch.
2. Check the new checkout from the original repository with git -C ../feature-work status. This reports the state of the worktree directory, not the original checkout.
3. Make sure the directory is accessible from the Project or computer where Elowen will work.

Git refuses to check out a branch already checked out in another worktree. A worktree also relies on the original repository's Git metadata; do not move its directory independently.

Use the worktree

1. In the CLI, run elowen chat from the worktree directory, or use /cd <path> in an existing CLI conversation.
2. In a managed Project, ask Elowen to use the Project tool's worktrees or worktree_create operation.
3. Check the selected Project and directory before asking for edits. Commit changes in that checkout as usual.

A managed worktree stays inside its Project's environment and does not move the conversation to a different Project. Local worktrees are managed by Git; Elowen does not keep a separate registry for them.

Remove the worktree

1. Keep or commit any changes you need.
2. From the repository, run git worktree remove <path> for a local worktree.
3. Check git worktree list to confirm it is gone.

Git may refuse removal when the worktree contains uncommitted changes; inspect them and decide what to preserve rather than forcing removal.

Related guides

See Projects, Environments & GitHub for the Project workflow, and CLI for local conversations.