Megjelent az OpenCode 2.0 a közös háttérszolgáltatással

We’re so glad you’re here. You can expect all the best TNS content to arrive Monday through Friday to keep you on top of the news and at the top of your game. Check your inbox for a confirmation email where you can adjust your preferences and even join additional groups. Follow TNS on your favorite social media networks. Check out the latest featured and trending stories while you wait for your first TNS newsletter. OpenCode 2.0 is getting a formal unpacking today, some three months after its public beta launch. The sizable architectural upgrade introduces a shared background service connecting its terminal, web and desktop interfaces, alongside a rebuilt API, a new embeddable SDK, and support for running subagents and shell commands in the background. In a blog post published on Monday, Anomaly, the company behind the open-source coding agent, calls the release a “major overhaul,” adding that it drew on the experiences of “millions of daily users” to build a more adaptable system capable of supporting an expanding range of agent capabilities. Anomaly has, in fact, been iterating on version 2.0 over the past few months, including publishing a detailed technical account of its revamped plugin architecture and hot-reloading capabilities in September. However, the drawn-out rollout has caused some confusion among developers, with questions about whether version 2.0 was officially stable yet, and complaints about missing release notes, even as updates kept shipping. Monday’s announcement, alongside the official changelog’s switch to the 2.x series, effectively signals that version 2 is now OpenCode’s main release. In tandem, the company is also offering a broader explanation of the technical decisions behind the upgrade. By way of a brief recap, OpenCode’s origins lie in the world of serverless development. Anomaly founders Jay V and Frank Wang previously created Serverless Stack (SST), an open-source framework for building and deploying applications on Amazon Web Services (AWS). Dax Raad, another prominent figure in OpenCode’s development, was also part of the SST team. Since its 2025 debut, OpenCode has gained a fervent following among developers looking for greater freedom over the AI models powering their coding tools. That became particularly pertinent in January when Anthropic began preventing third-party agents from using Claude Pro and Max subscription credentials, forcing affected developers to find alternative ways of accessing Claude or switch providers. As Janakiram MSV reported for The New Stack in May, these restrictions coincided with a surge of interest in OpenCode, which allows developers to switch between competing AI models. Today, the OpenCode GitHub repository has accumulated north of 212,000 stars and almost 30,000 forks. More broadly, there are signs of growing commercial interest in this category of coding agents. In July, Anaconda acquired Kilo, another such open-source coding agent that allows developers to choose their preferred AI provider. Interestingly, Kilo had already rebuilt its command-line interface and VS Code extension using OpenCode, demonstrating how the latter was finding a role inside other developer tools. With version 2.0, Anomaly has laid out how it has reworked OpenCode’s underlying architecture to accommodate a wider range of use cases. Arguably, the most significant change concerns how the coding agent runs, and how its different interfaces connect to it. Anomaly says the plumbing for a client/server setup has been in OpenCode from the start, though few beyond power users went out of their way to use it. With version 2.0, the server now starts automatically as a single background process on the developer’s machine, allowing OpenCode’s terminal, browser and desktop interfaces to communicate with the same underlying service. This means developers can access and manage their coding sessions through different interfaces, while the service handles the underlying execution. S