OpenCode 2.0, a major update to the open-source automation platform, introduces a suite of new features designed to streamline agent workflows and improve system integration. The release centers on architectural enhancements that simplify deployment and broaden compatibility across diverse environments.

The platform has transitioned from a client/server model previously reliant on manual configuration to a unified background process that operates automatically. This central service now serves as the foundation for all interfaces, including terminal-based interfaces, web dashboards, and desktop applications. Users can now interact with OpenCode through multiple entry points without managing separate service instances.

A key advancement is the overhaul of the application programming interface (API). The previous version had evolved organically through iterative use, resulting in a fragmented structure. The new API was rebuilt from the ground up after analyzing usage patterns across millions of daily users. It now supports a broader range of operations and includes built-in awareness of its own functionality, enabling actions such as migrating active sessions into version control worktrees during initialization.

The updated client library, @opencode/client, introduces native support for both browser-based JavaScript and Effect-based programming paradigms. This allows developers to create custom automation scripts that automatically locate and connect to the local service instance. The platform also facilitates interoperability through standardized API endpoints, enabling integration with external applications via command-line tools or direct service calls.

New capabilities include background processing features that allow primary agents to delegate tasks to secondary agents or execute asynchronous shell commands without interrupting user interaction. This architecture supports more complex workflows while maintaining responsiveness. Additionally, the platform now supports hot-reloading of plugins, enabling users to develop and implement custom extensions during active sessions.

The @opencode/sdk package provides access to the same underlying codebase used by the command-line interface, allowing developers to embed OpenCode functionality within specialized server environments or deploy customized versions on platforms like Durable Objects. The SDK includes both traditional and experimental API approaches, with the latter currently under active development.

Migration to version 2.0 requires attention to compatibility considerations. Existing plugins from the 1.x series are not directly compatible due to fundamental changes in the server API and configuration structure. Configuration files have been reorganized, with the previous tui.json format replaced by a new json-based system. Users upgrading the command-line tool should ensure they are running the latest 1.x version before executing the opencode upgrade --major command.

The update is available through standard channels, with desktop application updates accessible via the project's official download portal. Comprehensive migration documentation is provided to assist users in transitioning their existing workflows to the new architecture.