Use case
Git worktrees for AI coding agents
Canopy turns git worktrees into a visible workspace for parallel Claude Code, Gemini CLI, Codex, and OpenCode sessions.
Why worktrees fit AI agent workflows
AI coding agents often need freedom to edit files, run tests, and iterate. Git worktrees give each task a separate working directory while still sharing the same repository history.
- One branch can change files without interfering with another branch.
- Each worktree can keep its own terminal and agent session.
- Reviewers can inspect diffs per branch before merging.
Canopy makes existing worktrees visible
Canopy lists worktrees in a sidebar and lets you create new ones from the desktop app. You can still use git worktree commands in your terminal; Canopy works with the repository state rather than hiding it.
Browser tabs are per worktree
Each worktree has its own browser tab for testing the branch. Saved credentials and login storage are shared across Canopy as one browser tool, so the app does not promise full browser-profile isolation.
Questions
- Can I manage worktrees created outside Canopy?
- Yes. Canopy reads the git worktree list for the project, so existing worktrees can appear alongside ones created in the app.
- Do browser logins stay separate by worktree?
- No. Browser tabs are assigned to worktrees, but saved credentials and login storage are shared across Canopy.