OpenCode 2.0

TL;DR

Buying for a business?Offer from Amazon

Get business pricing on tech for your team

• Business-only prices and quantity discounts
• Tax-exempt purchasing
• Multiple users, one account, clear invoices

Create a free Business account →Free to register

As an affiliate, we earn on qualifying purchases.Hide

OpenCode 2.0 is a major overhaul of the coding-agent platform, adding a background service shared across its interfaces, a redesigned API and new ways to run tools and work asynchronously. The release also changes plugin and configuration compatibility: 1.0 plugins will not work in 2.0, and the server API has been replaced.

OpenCode 2.0 is a major overhaul of the coding-agent platform, introducing a single background service shared by its terminal, web and desktop interfaces, alongside a rebuilt API and new agent workflows. The release matters to developers who automate or extend OpenCode, but it includes breaking changes: version 1.0 plugins will not work, and the server API has been replaced.

The release notes say the local service now starts as one background process when OpenCode is used. The terminal UI, web interface and desktop app connect to that same process, rather than running independently. The project says its programmatic client, @opencode/client, can discover the local service automatically; users can also call it through CLI commands beginning with opencode api. The service can be exposed to other hosts and accessed using the pairing flow.

OpenCode says it rebuilt its API after reviewing use cases drawn from its daily user base. The release includes a JavaScript interpreter package, @opencode/codemode, which turns MCP servers and OpenAPI endpoints into functions an agent can use in scripts. According to the project, this allows an agent to combine calls—for example, using one tool’s results as input to another—in a single round trip. MCP servers are opted into code mode by default in version 2.0.

The release also adds background subagents and asynchronous shell commands, allowing work to continue while the main agent remains available for further prompts. OpenCode says users can start a subagent manually, including with another model, and move slow-running foreground work into the background. The project reports more than 80 internal plugins, says TUI plugins are now stable, and adds an SDK for using OpenCode as a library. Those are release-note descriptions; the supplied material does not include independent performance measurements or comparative testing.

One Service, More Ways to Extend

The shared service gives OpenCode’s interfaces a common local process, which may make it easier for scripts and interactive sessions to work with the same running environment. Automatic discovery in the client could reduce setup for developers automating routine tasks, while the pairing feature provides a route for other hosts or applications to connect. The release notes say native apps using this flow are in development, but do not give a schedule.

Code mode and background execution also change how the agent can coordinate work. Rather than handling tools only through a sequence of separate calls, an agent can compose operations in a script, while other tasks run without blocking the foreground session. These capabilities may be useful in workflows involving multiple tools or long-running commands. The project describes the intended behavior, but provides no measured results showing how much faster or more reliable those workflows are.

For teams with existing extensions, the migration cost is immediate: 1.0 plugins are incompatible with 2.0, and API integrations may need updating. That makes the release relevant not just as a feature update, but as a platform change that developers should check before upgrading.

From Version 1.0 to 2.0

OpenCode says it adopted a client/server architecture from the beginning, though the release notes say it was previously used mostly by more advanced users rather than being the default experience. Version 2.0 makes the local service central to the terminal, web and desktop applications.

The project describes the earlier API as having grown piecemeal as developers learned more about agent use cases. It says the new version starts over with a redesigned API and client package. OpenCode also says it built nearly every version 2.0 feature as an internal plugin, a choice intended to keep the plugin interface in use and maintained. The release notes do not provide a migration timeline or a detailed list of every change.

To upgrade the CLI, the project instructs users to first install the latest 1.x release and then run opencode upgrade –major. Desktop users are directed to download the latest app. The notes identify two specific breaking changes: 1.0 plugins do not work in 2.0, and the server API is completely different. They also say the tui.json configuration has moved to JSON, while describing many other changes as backward-compatible.

““In 2.0 this server now automatically runs as a single background process on your machine.””

— OpenCode 2.0 release notes

Compatibility and Performance Questions

The release notes do not give an exact publication date, migration deadline or full inventory of changes beyond the named compatibility issues. They also do not quantify performance improvements, despite describing performance work, or provide independent test results for the new service, code mode or background workflows. The project’s statements about daily users and the benefits of the redesign are its own descriptions, not independently verified measurements.

It is also unclear how much effort particular integrations will need to move to the new API, and whether users can keep existing plugins running through a compatibility layer; the notes say 1.0 plugins will not work in 2.0 but do not describe a workaround. The release says the optional Effect-based SDK API remains in development, so its final form and stability are not settled in the supplied material.

Upgrade Checks and SDK Development

Users planning to upgrade should review the project’s migration documentation, check whether their plugins depend on the 1.0 API, and confirm that scripts or services using the old server API are ready for changes. OpenCode recommends running the CLI upgrade from the latest 1.x version with opencode upgrade –major; desktop users should install the latest release from the project’s download page.

Further developments include native applications that use the pairing flow and continued work on the Effect-based SDK API. The release notes do not give dates for either. The immediate next step for existing users is to assess compatibility before upgrading, while the project’s subsequent updates should clarify migration details and the status of those in-development features.

Key Questions

What is new in OpenCode 2.0?

OpenCode 2.0 adds a shared background service, a redesigned API and client, code mode for composing tool calls, background subagents and shell commands, expanded plugin support, and an SDK for using OpenCode as a library.

Will OpenCode 1.0 plugins work in version 2.0?

No. The release notes explicitly say 1.0 plugins will not work in OpenCode 2.0. Plugin developers should review the new plugin documentation before upgrading.

How do users upgrade the CLI?

OpenCode says to first move to the latest 1.x release, then run opencode upgrade –major. Desktop users are directed to download the latest app.

What is OpenCode code mode?

Code mode uses the @opencode/codemode package to make MCP servers and OpenAPI endpoints available as functions an agent can call in JavaScript scripts. OpenCode says this lets an agent combine tool operations rather than making each call separately.

Are the performance gains independently verified?

The supplied release notes describe performance improvements but give no measurements or independent test results. The extent of any gains is not established by the provided material.

Source: hn