OpenCode 2.2.6 adds MCP pooling and worktree runs

OpenCode 2.2.6 was published on GitHub on November 6, 2026 (UTC). The headline features are opt-in MCP connection pooling and two new flags for scripted runs, --worktree and --archived. The change most likely to affect CI is quieter: opencode run now waits for every background job its prompt started before it exits, with no time limit.

Release facts

What changed

• Shared MCP connections. Set pool: true on an MCP server and projects with the same setup share one connection, which the notes say means fewer processes and faster starts.
• Worktree runs. opencode run -w starts the session in a new git worktree, and --worktree=<name> names it. It cannot be combined with --continue or --session.
• Archived runs. opencode run --archived creates the session already archived, so CI and scripted sessions stay out of the inbox, the session lists and --continue.
• GUI plugins. Plugins can add color themes, render or add actions to fenced code blocks through new CodeBlock and CodeBlockAction registries, and use native settings and menu components.
• Mobile composer dock. On phones and tablets, composer actions move to a touch dock above the keyboard with 44px targets.
• Experimental Code Mode VM. A bytecode VM for Code Mode is off by default; enable it with experimental.codemode_vm: true or OPENCODE_FLAGS=codemode_vm.

The CI change, in practice

In 2.2.6, opencode run waits for the background shell commands, subagents and image jobs its prompt started. While it waits it prints waiting for N background job(s) (a background_wait event with --format json), and lets the model respond to their results. There is no time limit. If a prompt starts a dev server or a file watcher, the run stays open until you press Ctrl+C or send SIGTERM, so set a job timeout in CI. SIGTERM now cancels the session and its background jobs and exits with code 143.

Security fixes

• The server API now serves file reads and media as sandboxed downloads and refuses cross-site requests to /api/* from disallowed origins, so a file in your project cannot run scripts on the server's origin.
• Webfetch and Code Mode fetch reject URLs that contain credentials, and Code Mode checks every redirect against your webfetch rules.
• session_move asks for external_directory permission before leaving the current project.

Questions

Why does opencode run hang in CI after upgrading? Most likely a background job, such as a dev server, is still running. Version 2.2.6 waits for all background jobs with no time limit, so add a timeout or stop the job in your prompt.

Is MCP pooling on by default? No. It is opt-in per server with pool: true.

How do I keep CI sessions out of my session list? Add --archived to opencode run.

See the OpenCode hub, the previous OpenCode 2.2.3 to 2.2.5 update and the OpenCode vs Cline vs Aider comparison.