OpenCode 2.0 Release Notes: What's New

Core Architecture Overhaul

OpenCode 2.0 shifts from a transient client/server model to a persistent background process. By running as a single daemon on the host machine, the service ensures that the TUI, web interface, and desktop applications all communicate with a unified state. This architecture allows programmatic clients—such as @opencode/client—to automatically discover the local service, facilitating seamless integration for scheduled tasks and remote host connections.

Enhanced Agentic Capabilities

OpenCode 2.0 introduces "Code Mode," a feature powered by a minimal JavaScript interpreter that allows agents to execute scripts natively. By ingesting MCP servers or OpenAPI endpoints, the agent can compose multiple tool calls into a single script, reducing round-trip latency. Additionally, the system now supports background sub-agents and asynchronous shell commands. This allows a primary agent to delegate tasks to secondary models or long-running processes without blocking the main interaction loop, enabling more complex orchestration.

Plugin System and SDK

To ensure long-term stability, the OpenCode 2.0 team implemented nearly all core features as internal plugins, resulting in a library of over 80 stable, hot-reloadable plugins. The platform now exposes its functionality through the @opencode/sdk package, allowing developers to build custom versions of the harness that run in specialized environments, such as Durable Objects, while maintaining compatibility with the standard OpenCode server protocol.

Community Feedback and Implementation Insights

While users have praised the improved plugin system and the robust client/server model, the release has faced scrutiny regarding its resource footprint and installation experience. Community discussion highlights several key areas of concern and appreciation:

Performance and Bloat: Several users noted significant memory consumption, with some reporting that the tool can be "heavy" compared to lighter alternatives. Concerns were also raised regarding the default behavior of storing large volumes of session logs.
Installer Experience: Early adopters reported that the curl | sh installation script suffered from extreme latency, which was attributed to the overhead of rendering progress bars.
Security and Sandboxing: The transition to a background process has changed how sandboxing works, with some users reporting that previous security wrappers became ineffective after the upgrade. There is also ongoing debate regarding the security implications of mandatory remote configuration loading.
Developer Experience: Many users appreciate the ability to use custom models and the flexibility of the new plugin architecture, though some have expressed frustration with the complexity of migrating from version 1.0.

"The background task / subagent feature and the ability to specify a model when starting a subagent are so far my favorite improvements. Small things but make huge QoL difference in everyday development." — Community User

"A commit born from 'Claude, please make the installer look sick as fuck with loading bars and stuff' will always be preferred by the developers over a commit that reverts such a change for a 10 MB drop in memory use." — Community User

Upgrading to 2.0

Upgrading requires a transition to the new API, as 1.0 plugins are incompatible with the 2.0 architecture. Users are advised to run opencode upgrade --major for the CLI or download the latest desktop installer. The migration documentation provides automated tools to assist in updating tui.json configurations and adapting to the new server-side protocols.