How do I upgrade from OpenCode 1.x to OpenCode 2.0?

OpenCode 2.0 is reached from the CLI by first updating to the latest 1.x release, then running opencode upgrade --major. Version 1.19.0 stopped installing updates automatically for this reason. Desktop users download the latest app from the OpenCode download page. The migration guide also suggests asking OpenCode itself to convert your setup.

Will my OpenCode 1.x plugins and config still work?

OpenCode 2.0 does not run version 1 plugins, because the plugin API is new, and integrations that call the server API must move to the @opencode/client package. Existing config files are read from the same locations and normalized in memory, so they keep working. Converting them to the native 2.0 shape is optional.

Does OpenCode 2.0 still read CLAUDE.md files?

OpenCode 2.0 discovers only AGENTS.md as its instruction file, according to the migration guide. The CLAUDE.md fallback that version 1 supported is gone, so project guidance should move into AGENTS.md. The guide also notes that version 2 keeps LSP config but does not run language servers or show LSP diagnostics.

Can I use OpenCode 2.0 as a library in my own app?

OpenCode 2.0 ships an SDK package, @opencode/sdk, that lets developers use OpenCode as a library. A separate @opencode/client package offers clients for vanilla JavaScript and Effect to talk to the rebuilt server API. Because every client connects to one background service, the same sessions can serve the terminal, web and desktop apps.

Anomaly · 2026-10-12 · major

OpenCode 2.0 — the open-source coding agent becomes a background service

OpenCode 2.0 runs one background server that the terminal, web and desktop apps share. It adds a rebuilt API, Code Mode, background subagents and an SDK. Version 1 plugins no longer work.

OpenCode 2.0 announcement card from Anomaly

OpenCode 2.0 turns the open-source terminal coding agent into a shared service with an API, SDK and background work.

Quick facts

Maker	Anomaly
License	MIT
Clients	Terminal, web and desktop
Upgrade	opencode upgrade --major (from latest 1.x)
New packages	@opencode/sdk, @opencode/client
Breaking	v1 plugins, server API, terminal config

What is it?

OpenCode 2.0 is a major overhaul of the open-source AI coding agent from Anomaly. The agent now runs as a single background service, and the terminal UI, web interface and desktop app all connect to it. The team says the release is built on feedback from millions of daily users.

How does it work?

A rebuilt server API sits at the center, and OpenCode can call its own API, for example to move a session into a git worktree. Code Mode adds a small JavaScript interpreter so the agent can chain several tool calls in one script, with all MCP servers opted in by default. Pressing Ctrl+B moves running subagents or shell commands to the background, and more than 80 features are now internal plugins that hot-reload.

Why does it matter?

Developers who build on the coding agent get a stable plugin API and an SDK, so they can embed it in their own tools instead of driving a terminal. The cost is a migration: version 1 plugins and server integrations must be ported to the new APIs.

Who is it for?

developers using or building on terminal coding agents

Frequently asked questions

How do I upgrade from OpenCode 1.x to OpenCode 2.0?: OpenCode 2.0 is reached from the CLI by first updating to the latest 1.x release, then running opencode upgrade --major. Version 1.19.0 stopped installing updates automatically for this reason. Desktop users download the latest app from the OpenCode download page. The migration guide also suggests asking OpenCode itself to convert your setup.
Will my OpenCode 1.x plugins and config still work?: OpenCode 2.0 does not run version 1 plugins, because the plugin API is new, and integrations that call the server API must move to the @opencode/client package. Existing config files are read from the same locations and normalized in memory, so they keep working. Converting them to the native 2.0 shape is optional.
Does OpenCode 2.0 still read CLAUDE.md files?: OpenCode 2.0 discovers only AGENTS.md as its instruction file, according to the migration guide. The CLAUDE.md fallback that version 1 supported is gone, so project guidance should move into AGENTS.md. The guide also notes that version 2 keeps LSP config but does not run language servers or show LSP diagnostics.
Can I use OpenCode 2.0 as a library in my own app?: OpenCode 2.0 ships an SDK package, @opencode/sdk, that lets developers use OpenCode as a library. A separate @opencode/client package offers clients for vanilla JavaScript and Effect to talk to the rebuilt server API. Because every client connects to one background service, the same sessions can serve the terminal, web and desktop apps.

Try it

opencode upgrade --major