opencode-worktree vs worktrunk
Git worktree tools for OpenCode sessions and parallel development
opencode-worktree automates isolated Git worktrees for OpenCode V1 and opens a separate terminal session for each one. worktrunk is a Rust CLI for creating, switching between, and cleaning up worktrees, with broader branch-oriented commands and workflow automation.
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.
worktrunk: Manage Git Worktrees for Parallel Development
Worktrunk is a Rust CLI that simplifies creating, switching between, and cleaning up Git worktrees. It suits developers running parallel tasks, especially with AI coding agents, who want consistent worktree workflows and automation.
| opencode-worktree | worktrunk | |
|---|---|---|
| Language | TypeScript | Rust |
| License | MIT | NOASSERTION |
| Stars | 728 | 8.7k |
| Forks | 42 | 315 |
| Last analyzed | Oct 11, 2026 | Oct 4, 2026 |
Key differences
- opencode-worktree is a TypeScript plugin for OpenCode V1; worktrunk is a standalone Rust CLI for Git worktree management.
- opencode-worktree creates a worktree and launches OpenCode in a new terminal, while worktrunk provides commands to create, switch, list, and remove worktrees.
- opencode-worktree supports configured file copying or symlinking and post-create or pre-delete hooks; worktrunk offers hooks for events such as worktree creation and merges.
- worktrunk includes merge workflows, commit-message generation, shell integration, and build-cache sharing on APFS, btrfs, and XFS; these are not listed as opencode-worktree features.
- opencode-worktree is archived, targets OpenCode V1, and has no planned V2 port; worktrunk is not archived.
- opencode-worktree reports an MIT license, while worktrunk reports NOASSERTION in repository metadata and displays an MIT OR Apache-2.0 README badge.
Choose opencode-worktree if you…
- need worktree creation tied directly to OpenCode V1 sessions in separate terminals.
- want configured files or directories copied or symlinked into new worktrees.
- need project setup or teardown hooks and understand that deletion commits changes before removing a worktree.
Choose worktrunk if you…
- want a CLI for creating, switching between, listing, and removing Git worktrees.
- run parallel coding tasks or agents and want to launch commands after switching into a worktree.
- need workflow features such as hooks, merge workflows, shell integration, or supported build-cache sharing.
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.