TL;DR
Get business pricing on tech for your team
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
OpenCode 2.0 is a major overhaul that makes its command-line, web and desktop interfaces use one local background service. The release also introduces a rebuilt API, JavaScript-based tool composition, background agents and shell commands, and expanded plugin and SDK support; existing 1.0 plugins will not work with 2.0.
OpenCode has released version 2.0, a major overhaul of its coding-agent platform that puts its command-line interface, web interface and desktop app on a single local background service. The release also changes how developers connect tools and automate work, while introducing compatibility breaks for 1.0 plugins and the previous server API.
OpenCode says the service runs as one background process on a user’s machine, with its different interfaces communicating with that shared process. The company says the programmatic @opencode/client package can discover the local service automatically, while developers can also use CLI commands under opencode api. The release notes describe a pairing option for connections from other hosts or applications; native apps using that flow are still in development.
The release replaces the previous API, which OpenCode says had grown in an ad hoc way, with a redesigned one intended to support a broader range of use cases. A new package, @opencode/client, provides JavaScript and Effect-based clients. OpenCode also says the agent can use its own API for tasks such as moving a session into a Git worktree when starting new work.
Another addition, @opencode/codemode, is described as a minimal JavaScript interpreter for composing calls to MCP servers and OpenAPI endpoints. According to the release notes, an agent can put multiple tool calls and operations into a script rather than making each call separately. OpenCode says MCP servers use code mode by default in version 2.0, with the aim of keeping context use low even when many servers are configured.
One Service, More Ways to Automate
Using one local service across the CLI, web and desktop interfaces could make it easier to keep work and automation connected, rather than treating each interface as a separate environment. The client package and CLI API commands also give developers ways to build scripts around OpenCode; the release notes specifically point to scheduled tasks as one use case.
Code mode and background execution change how the agent can coordinate work. OpenCode says agents can run scripts that combine tool results and launch subagents or shell commands without blocking the main interaction. Those features may help with longer or multi-step coding tasks, although the source material does not provide independent performance measurements or comparative results.
The changes also affect teams maintaining extensions and integrations. Since the server API has been replaced and 1.0 plugins are incompatible, upgrading may require migration work. The broader plugin system and SDK could give developers more ways to customize OpenCode, but the practical benefits will depend on their existing setups and the quality of compatibility updates.
As an affiliate, we earn on qualifying purchases.
OpenCode says it has used a client/server design since its early versions, but that architecture was mostly used by power users rather than being the default experience. Version 2.0 makes the local service central: the terminal interface, web interface and desktop app now connect to the same process, according to the release notes.
The overhaul also extends the platform’s existing plugin approach. OpenCode says it implemented nearly every 2.0 feature internally as a plugin and now has more than 80 plugins. It has moved TUI plugins from experimental to stable status and says features can be hot-reloaded, allowing a plugin created during a session to be used immediately.
OpenCode presents the SDK as another route for using the same underlying code as its CLI in custom environments, including servers and Durable Objects. It says those implementations can connect through the standard OpenCode server protocol. The optional Effect-based API is available but remains in development, according to the release notes.
““In 2.0 this server now automatically runs as a single background process on your machine.””
— OpenCode, in its version 2.0 release notes
As an affiliate, we earn on qualifying purchases.
Migration and Feature Readiness
The release notes do not give a publication date, detailed migration timeline, or independent performance data for the new system. They also do not quantify how much code mode reduces context use or how much faster combined tool calls may be in practice; those benefits are presented by OpenCode as design aims.
Some compatibility details remain broad. OpenCode says there are other changes beyond the named breaking changes, while describing the rest as backwards compatible, but the source does not enumerate every affected configuration or integration. The Effect-based API is still evolving, and native apps built around the pairing flow are described as being in development. Users will need to consult the release documentation to determine how the changes apply to their projects.
As an affiliate, we earn on qualifying purchases.
Upgrade and Check Compatibility
OpenCode’s stated upgrade path for the CLI is to move to the latest 1.x release first, then run opencode upgrade –major. Desktop users are directed to download the latest app. The company says users can point OpenCode at its migration documentation to help handle configuration changes.
Before upgrading, developers who rely on custom plugins or integrations should account for the 1.0 plugin incompatibility and the completely changed server API. OpenCode has not given a schedule in the supplied release notes for the native apps or for the Effect API to leave development. Further details on those items, and on migration issues found by users, remain pending.
As an affiliate, we earn on qualifying purchases.
Key Questions
What is OpenCode 2.0?
OpenCode 2.0 is a major overhaul of the coding-agent platform. It adds a shared local service, a redesigned API, code-mode tool composition, background tasks and expanded plugin and SDK support.
What changes for current OpenCode users?
The command-line, web and desktop interfaces now connect to one local background process, according to OpenCode. Users should also account for breaking changes: 1.0 plugins do not work in 2.0, and the server API has been replaced.
How does code mode work?
OpenCode’s @opencode/codemode package lets the agent write JavaScript scripts that call MCP servers or OpenAPI endpoints and combine operations. OpenCode says MCP servers opt into this mode by default in version 2.0.
How do users upgrade the CLI?
OpenCode says to first install the latest 1.x release, then run opencode upgrade –major. Desktop users are directed to download the latest version. The release notes also recommend consulting the migration documentation.
Are all OpenCode 2.0 features final?
No. OpenCode says the optional Effect-based API is still in development, and native apps that use the pairing flow are in the works. The supplied release notes do not state when those items will be complete.
Source: hn
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
