Skip to content
OpenChamber
↑↓Navigate ↵Open escClose

Worktree Sessions

A worktree session runs in its own checked-out copy of your repo, on its own branch (a git worktree). That keeps parallel sessions from stepping on each other’s files — one can refactor while another fixes a bug, with no switching back and forth.

Create one

  1. Open the new-worktree dialog: pick New worktree… in the branch menu above the composer when you start a new session, or use the worktree button on a project row in the sidebar.
  2. Under Start from, pick one:
    • new branch — name the branch
    • existing branch — check out a branch you already have
    • PR or issue — pick one from GitHub, Linear or an extension; the branch is named after it (a PR checks out its own branch), and the item is attached to your first message
  3. Check Based on (the branch a new one starts from, the project’s current branch by default) and Folder name; change them only if you need to.
  4. Create it. If the project has setup commands, they run right after.

OpenChamber makes the branch, sets up the folder, and opens a new session there, ready for your first message. You can also kick one off straight from a todo or a GitHub issue or PR.

To skip the questions, pick Quick worktree in the same branch menu: OpenChamber names the branch for you and points the new session at it.

Bring the work back

When the work is good, use Integrate in the Git view to bring the worktree’s commits onto another branch (like main). If a change conflicts, you can hand the conflict to the agent to resolve.

Clean up

Deleting or archiving the session can remove the worktree. You choose whether to also delete the branch — local, and remote if there is one. Nothing is deleted without you asking.

If something looks off

A worktree can need attention if its folder went missing, its branch is in a detached state, or a merge or rebase is half-finished. OpenChamber flags these so you can fix them — see Worktrees & Git.