opencode-worktree: Automate Isolated Git Worktrees for OpenCode

Overview

opencode-worktree is a plugin for OpenCode V1 that turns Git worktree creation and cleanup into an AI-driven workflow. Creating a worktree can sync files, run setup hooks, and open a terminal with OpenCode ready; deleting one can run cleanup hooks, commit changes, and remove the worktree.

It is aimed at CLI-first developers who want AI-assisted tasks isolated from their main checkout without handling each setup step manually. The project is retired and has no planned OpenCode V2 port, so it is relevant mainly to existing OpenCode V1 users or people maintaining a fork.

Key Features

• Adds worktree_create and worktree_delete tools for creating and removing Git worktrees.
• Opens a new terminal session with OpenCode in each created worktree.
• Copies selected files and symlinks configured directories, such as environment files and dependencies.
• Supports post-create and pre-delete shell hooks for project setup and cleanup.
• Stores worktrees outside the repository under OpenCode's local data directory.
• Supports common terminals across macOS, Linux, and Windows, as well as tmux and cmux workflows.
• Can commit changes automatically before removing a worktree.

Use Cases

• OpenCode V1 users can delegate a feature experiment to an isolated worktree while keeping their primary checkout untouched.
• CLI-first developers can start separate OpenCode sessions for parallel tasks without manually opening and configuring terminals.
• Teams with per-worktree setup needs can sync selected files and run commands such as dependency installation or container startup.
• Existing users who need to keep a legacy V1 workflow running can use the published code as-is or maintain a fork.

Getting Started

For the legacy OpenCode V1 installation, the README gives this OCX command:

ocx add kdco/worktree --from https://registry.kdco.dev

See the README for configuration and manual installation details. The repository advises OpenCode V2 users to use its native workspace/worktree workflows or ordinary Git worktrees instead.

Alternatives

• agent-worktrees: It manages isolated worktrees for Claude Code from VS Code, rather than creating and launching OpenCode worktrees from a plugin.

Considerations

• The repository is archived and explicitly retired for OpenCode V1; the owners do not plan a V2 port. Its lifecycle hooks, automatic terminal handoff, and OCX environment bridge are not part of the V2 migration.
• The project has had recent commits, but no releases in the past year. Maintenance and source synchronization have ended, and the measured contributor history is concentrated in one person.
• Shell hooks run with the user's privileges in the worktree directory. Review configured commands before using them.
• Terminal behavior varies by environment. Some terminals open a new window rather than a tab, and some integrations require additional terminal configuration.
• The README says worktrees can also be used in OpenCode Desktop, but automatic terminal spawning is a CLI-oriented feature.