OpenCode 2.0 reached public beta in July, and Anomaly has now formally detailed the architectural overhaul. The redesign introduces a unified background service that links the terminal, web and desktop interfaces, along with a completely rebuilt API, a new embeddable SDK, and the ability to run subagents and shell commands asynchronously.

In a blog post on Monday, Anomaly, the company behind the open-source coding agent, characterized the release as a "major overhaul," noting that it incorporated feedback from "millions of daily users" to create a more flexible architecture capable of supporting an expanding set of agent features.

Anomaly has been refining version 2.0 throughout the past several months, including releasing a technical breakdown of its redesigned plugin architecture and hot-reloading functionality in September. The gradual rollout generated some uncertainty among developers about whether version 2.0 had achieved official stability, and some raised concerns about incomplete release notes even as new updates continued to ship.

Monday's announcement, combined with the official changelog's transition to the 2.x series, confirms that version 2 is now OpenCode's primary release. The company is simultaneously providing a comprehensive breakdown of the technical reasoning underlying the upgrade.

OpenCode's background

OpenCode traces its roots to serverless development. Anomaly co-founders Jay V and Frank Wang previously developed Serverless Stack (SST), an open-source tool for constructing and deploying applications on Amazon Web Services (AWS). Dax Raad, another key contributor to OpenCode, was also involved with the SST project.

Since launching in 2025, OpenCode has attracted a dedicated developer community seeking more control over the AI models integrated into their coding tools. This became especially relevant in January when Anthropic started blocking third-party agents from accessing Claude Pro and Max subscription credentials, pushing affected developers to pursue alternative Claude access methods or switch to different providers.

As reported by Janakiram MSV for The New Stack in May, these limitations drove a notable uptick in OpenCode adoption, which enables developers to alternate between different AI models. The OpenCode GitHub repository now has surpassed 212,000 stars and nearly 30,000 forks.

The coding agent category is attracting growing commercial attention. Anaconda acquired Kilo in July, another open-source coding agent that lets developers select their preferred AI provider. Notably, Kilo had already reconstructed its command-line interface and VS Code extension using OpenCode, illustrating how the platform was becoming embedded in other developer tools.

Version 2.0 demonstrates how Anomaly has restructured OpenCode's core architecture to support a broader spectrum of use cases. The most transformative change involves the way the coding agent operates and how its various interfaces interact with it.

Single service, multiple interfaces

Anomaly notes that the infrastructure for a client/server model existed in OpenCode from the beginning, though only experienced users typically activated it.

In version 2.0, the server launches automatically as a single background process on the developer's computer, enabling OpenCode's terminal, browser and desktop interfaces to connect to the same underlying service.

This architecture allows developers to access and manage coding sessions across different interfaces, while the service manages the underlying operations. Scripts written using OpenCode's programmatic client can automatically locate and attach to the local service, making them suitable for recurring tasks. Developers can also make the service accessible to other machines and integrate it with external applications.

Developers can now start a session in OpenCode's terminal interface, continue working on it through the desktop or web app, and have their own scripts connect to the same underlying service

Anomaly

These structural modifications are paired with a complete redesign of OpenCode's API, which Anomaly acknowledges was constructed incrementally as the industry was still learning about agents.

The old API grew haphazardly as we and the world collectively learned what agents are and should be. It was bad.

Anomaly

The updated API grants agents greater autonomy over their operating environment. For instance, an agent can establish a Git worktree for a new task, move an existing session into that worktree, or detect and halt another session that has stalled. The API is now accessible through a new @opencode/client package, which works with standard JavaScript and Effect.

An embeddable SDK, released as @opencode/sdk, is another new addition, allowing developers to embed OpenCode into their own applications. It leverages the same underlying code as OpenCode's CLI, the company explains, letting developers build tailored versions of the agent for servers or platforms such as Cloudflare Durable Objects.

These implementations can interact with existing OpenCode clients via its standard server protocol, though Anomaly indicates the SDK is still under active development.

Code Mode and asynchronous execution

Version 2.0 modifies how agents work with external tools through the Model Context Protocol (MCP).

A new capability called Code Mode enables agents to compose JavaScript that invokes multiple tools and handles their output in a single operation. Constructed on a minimal JavaScript interpreter in the @opencode/codemode package, it transforms MCP servers and OpenAPI endpoints into callable functions for agents.

An agent could, for example, pull bug reports from GitHub, extract the pertinent details and generate corresponding tasks in Linear, all without requiring a separate model call for each step.

This approach carries particular weight for developers integrating agents with numerous external services, where tool specifications can occupy significant portions of a model's context window. Anomaly is setting Code Mode as the standard for all MCP servers in version 2.0, contending that it makes large-scale integrations more feasible.

This means you can add a thousand of them with minimal context bloat and your agent will discover and compose them to get things done

Anomaly

OpenCode 2.0 also adds background execution for subagents and shell commands, permitting developers to keep engaging with the main agent while other tasks proceed. A developer might, for instance, assign a code review to a subagent using a different AI model while maintaining focus on the primary work. Extended shell tasks, like running test suites or compiling applications, can run in parallel, with the primary agent receiving a signal upon completion.

A keyboard shortcut lets developers move an active foreground task to the background if it runs longer than anticipated.

The release also includes updates to OpenCode's plugin architecture. Anomaly has integrated more than 80 internal plugins, encompassing the majority of the functionality added in version 2.0, to strengthen the stability and maintainability of its plugin API.

Terminal interface plugins have graduated from experimental status to stable, and hot reloading support means OpenCode can construct and activate a new plugin during an active session without needing to restart.

There are compatibility considerations for current users. Plugins created for OpenCode 1.0 are incompatible with version 2.0, and integrations built on the earlier server API require modification.

Existing OpenCode 1.x users can move to version 2.0 by executing opencode upgrade --major from the command line or typing /update in the terminal interface. Per the October 11 release notes, automatic updates are no longer deployed, requiring users to manually trigger the upgrade.