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 of the coding agent, adding a shared background service, a redesigned API, script-based tool composition, background work and a more extensively used plugin system. The release also changes the server API and breaks compatibility with 1.0 plugins; users must upgrade from the latest 1.x CLI using a major-version command.
OpenCode 2.0 is a major overhaul of the coding agent, introducing a shared local service, a rebuilt API and new ways for agents to run tools and tasks in the background. The release matters to existing users and developers because it also includes breaking changes: 1.0 plugins will not work, and the server API has been replaced.
OpenCode says its client/server architecture now runs by default as one background process on a user’s machine. The terminal interface, web interface and desktop app connect to that service, while the programmatic @opencode/client package can discover it automatically. Users can also expose the service to other hosts and pair it with other applications, according to the release notes.
The team says it rebuilt the API after reviewing use cases from its daily users. The new release includes a JavaScript interpreter in @opencode/codemode, which turns MCP servers or OpenAPI endpoints into functions an agent can combine in scripts. OpenCode says this can let an agent call a tool, process its results and call another tool in one script, rather than making separate tool calls. MCP servers are opted into code mode by default in version 2.0.
Other changes include background subagents and asynchronous shell commands, allowing work to continue while a user keeps prompting the main agent. OpenCode also says it now has more than 80 internal plugins, and that TUI plugins have moved from experimental to stable. The new @opencode/sdk lets developers use the same code that powers the CLI as a library, including in server-based or specialized environments.
The shared service changes OpenCode from a tool whose client/server setup was mainly used by advanced users into a default part of how its interfaces and automation work together. For developers, automatic service discovery and the new client package could simplify scripts and scheduled tasks; the release notes describe those uses, but provide no comparative performance measurements.
Code mode and background execution address two practical limits in agent workflows: sequential tool calls and work that blocks further interaction. Script composition may reduce repeated calls when an agent needs to pass results between tools, while background tasks let a user continue working during longer operations. These are capabilities described by OpenCode, not independently measured productivity gains.
The plugin and SDK changes also make the release relevant beyond people using the built-in interface. Developers can build plugins or use OpenCode as a library, but the new API and plugin incompatibility mean that upgrading may require changes to existing integrations.
As an affiliate, we earn on qualifying purchases.
From Client Server to Version 2
OpenCode says it adopted a client/server model from the beginning, but the local server had largely been used by power users rather than running as the default shared process. Version 2.0 makes that service central to its terminal, web and desktop interfaces, and to programmatic access.
The release notes describe the API as having developed gradually as the team learned how people use agents. The team says it started over and reviewed a broad range of user scenarios. The announcement does not publish a migration-by-migration list in the supplied material, but it flags several changes users should account for: 1.0 plugins are incompatible, the server API is different, and the TUI configuration file has moved from tui.json to json. The team says other changes are backward compatible.
“In 2.0 this server now automatically runs as a single background process on your machine.”
— OpenCode release notes
software development plugin system
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Migration and Compatibility Questions
The supplied release notes do not specify a publication date, a complete inventory of changes, or how much migration work different users should expect. They say the server API is completely different and 1.0 plugins do not work, but do not detail compatibility for every third-party integration.
OpenCode describes code mode as using a minimal JavaScript interpreter and says it can handle many MCP servers with minimal context bloat. The announcement does not provide independent benchmarks, security assessments or quantified performance results for those claims. It also says the Effect-based SDK API remains in development, so its behavior may change.
As an affiliate, we earn on qualifying purchases.
Upgrade Steps and Developer Changes
For the CLI, OpenCode instructs users to first install the latest 1.x release, then run opencode upgrade –major. Desktop users are directed to download the latest app. The release notes also recommend pointing OpenCode at the migration documentation to help move existing configuration.
Users with custom plugins or software that depends on the old server API will need to check those integrations against the 2.0 documentation before upgrading. OpenCode says native apps that use the pairing flow are in the works, but the announcement gives no release date. The Effect-based SDK interface is also still under development.
background task automation software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What is new in OpenCode 2.0?
It adds a default shared background service, a redesigned API, code mode for composing tool calls in scripts, background subagents and shell commands, and expanded plugin and SDK support.
Will OpenCode 1.0 plugins work in version 2.0?
No. OpenCode’s release notes explicitly say 1.0 plugins will not work in 2.0. Plugin authors and users should check the new documentation for migration options.
How do CLI users upgrade?
OpenCode says to update to the latest 1.x release first, then run opencode upgrade –major. The notes also warn that the server API has changed and the TUI configuration file has moved.
What does code mode do?
The @opencode/codemode package converts MCP servers or OpenAPI endpoints into functions an agent can call in a JavaScript script. OpenCode says this lets agents combine tool calls and process results in a single script.
Is the new SDK fully stable?
The release notes say the Effect-based API offered with the SDK is still in development and may change. The announcement does not provide a general stability designation for every SDK feature.
Source: hn
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
