agent-worktrees vs opencode-worktree
Git worktree tools for Claude Code and OpenCode compared
agent-worktrees manages Claude Code agents and Git worktrees from a VS Code panel. opencode-worktree automates worktree setup and launches OpenCode V1 in separate terminals; it is archived, with no planned V2 port.
agent-worktrees: Manage Claude Agents Across Git Worktrees
A VS Code extension for starting and monitoring Claude Code agents in isolated Git worktrees. It brings agent status, worktree Git state, and optional GitHub pull request checks into one panel.
opencode-worktree: Automate Isolated Git Worktrees for OpenCode
An OpenCode V1 plugin that creates Git worktrees, syncs configured files, and launches each one in a separate terminal with OpenCode running. It is archived, with no planned OpenCode V2 port.
| agent-worktrees | opencode-worktree | |
|---|---|---|
| Language | TypeScript | TypeScript |
| License | MIT | MIT |
| Stars | 1 | 728 |
| Forks | 0 | 42 |
| Last analyzed | Oct 7, 2026 | Oct 11, 2026 |
Key differences
- agent-worktrees is a VS Code extension for monitoring and managing Claude Code sessions, while opencode-worktree is an OpenCode V1 plugin for worktree creation and cleanup.
- agent-worktrees shows agent activity and Git state in one panel; opencode-worktree can sync configured files, run shell hooks, and open a terminal with OpenCode running.
- agent-worktrees supports existing worktrees and creating a worktree with an agent; opencode-worktree provides dedicated create and delete tools and can commit changes before removal.
- agent-worktrees is not archived and is described as new and evolving; opencode-worktree is archived and has no planned OpenCode V2 port.
- Both projects use TypeScript and the MIT license, but their recorded popularity differs: agent-worktrees has 1 star and 0 forks, while opencode-worktree has 728 stars and 42 forks.
Choose agent-worktrees if you…
- manage several Claude Code sessions across Git worktrees from VS Code.
- monitor agent status and worktree Git state in one panel.
- use optional pull request checks alongside worktree management.
Choose opencode-worktree if you…
- use an existing OpenCode V1 workflow to automate worktree setup and cleanup.
- sync selected files and run setup or cleanup hooks for each worktree.
- launch separate OpenCode terminal sessions for isolated tasks.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.