Run OpenCode in parallel

What you get on top of the CLI

OpenCode works with many model providers, and you often want to try the same task two ways or run unrelated tasks at once. Doing that in one folder means agents editing the same files. Maestro gives every task its own isolated checkout and the tools to review it:

• Parallel workspaces. One git worktree and branch per workspace, and no cap on how many you open.
• A diff review loop. Read each workspace's changes, comment on lines, and send the comments back to OpenCode.
• Pull requests. Open a PR from a workspace branch without leaving the app.
• An editor and a preview. A Monaco-based editor with Jupyter notebook support, a terminal per workspace, and a built-in browser preview with freeze-frame annotations.
• Your phone. Maestro Web mirrors each workspace to a mobile web app, so you can follow a session and reply from anywhere while it runs on your machine.

How it works

Maestro runs OpenCode's non-interactive command, one process per message, inside the workspace's worktree:

opencode run [--continue] [--agent plan] "<your message>"

• Conversation continuity. After the first message, Maestro adds --continue, which picks up the last OpenCode session in that directory. Since every workspace is its own worktree directory, each workspace keeps its own conversation.
• Plan mode. The plan toggle runs the turn with OpenCode's built-in plan agent, which can't edit or write files, so it proposes changes without applying them.
• Models and providers. OpenCode chooses the provider and model from its own configuration; Maestro doesn't override it, so the picker shows "Default". Change models the way you normally do in OpenCode.
• Output. Maestro streams OpenCode's text output into the chat as it arrives. It shows as plain text rather than the structured tool-call steps you get with Claude Code or Codex.
• Your accounts. OpenCode stores provider credentials itself (in ~/.local/share/opencode/auth.json). Maestro reads that file only to show which providers are connected. Usage is billed by those providers under your accounts.
• What gets installed. Only Maestro. It uses the opencode on your PATH. If it's missing, Settings → Harnesses can install it and run opencode auth login in an in-app terminal.
• Remote machines. On an SSH project, opencode runs on the remote host.

Set it up

What about OpenCode's own desktop app?

The OpenCode team ships its own desktop app for macOS, Windows, and Linux as of September 2026 (opencode.ai/download), alongside the terminal UI and IDE extensions. If OpenCode is your only agent, start there.

Maestro is useful when you want git-worktree isolation for every session handled for you, a review-and-PR loop around each one, other agents such as Claude Code, Codex, or Cursor's agent CLI in the same window, or your sessions on your phone through Maestro Web.

The underlying technique is plain git; see running agents in parallel with git worktrees for a walkthrough that works with any CLI agent.