OpenCode 2.0 runs its terminal, desktop and web clients against one background process
Anomaly's OpenCode 2.0 puts its terminal, desktop and web apps on one background service, about three months after the beta began. The long rollout left developers unsure whether 2.0 was stable, so teams building on it should check the release state.
The Engineer · Build desk
Map of who reaches OpenCode's shared service: developers start a session in the terminal and continue it in the desktop or web app; scripts built with the programmatic client connect to the local service; developers can expose it to other machines and external applications.
- What's now possible capability Developers in live sessions Can start a session in the terminal interface and continue it through the desktop or web app, claim 10
- What's now possible capability Scripts and scheduled tasks Scripts built with the programmatic client can automatically discover and connect to the local service, claim 7
- Who's exposed exposure Other machines, external apps Developers can expose the service to other machines and pair it with external applications, claim 8
| Who | How | Kind | Claim |
|---|---|---|---|
| Developers in live sessions | Can start a session in the terminal interface and continue it through the desktop or web app | capability | 10 |
| Scripts and scheduled tasks | Scripts built with the programmatic client can automatically discover and connect to the local service | capability | 7 |
| Other machines, external apps | Developers can expose the service to other machines and pair it with external applications | exposure | 8 |
What happened
- Anomaly's Monday blog post calls the release a "major overhaul" and says it drew on the experience of "millions of daily users".
- Beyond the shared service, 2.0 adds a rebuilt API, an embeddable SDK, and support for running subagents and shell commands in the background.
- The New Stack says Monday's announcement and the changelog's switch to the 2.x series effectively signal that version 2 is now OpenCode's main release.
Why it matters
- Who has to decide decision Teams building on the rebuilt API or SDK should pin a 2.x build they have tested, since main-release status is The New Stack's reading of a changelog switch.
- Who's exposed exposure A service that runs subagents and shell commands and can be exposed to other machines needs its default bind address and authentication checked before anyone turns that on.
- What's now possible capability Scheduled jobs and external applications can connect to the same service a developer uses interactively, so automation can share an agent runtime with the live session.
Next story · Build · Oct 5
OpenAI opens its 28-day Codex pledge by speeding GPT-6 Astra and Sol to about 50 tokens a secondConfirmed2 publishers
Anomaly says OpenCode has had the client/server plumbing since its first release, but outside of power users hardly anyone sought it out [4]. What 2.0 changes is the default. The server now starts automatically as a single background process on the developer's machine, and the terminal, browser and desktop interfaces all communicate with it [5].
The service handles execution, and the interfaces are different ways to manage sessions on it [6]. A session started in the terminal can therefore be continued in the desktop or web app [10]. One process per machine is tidy until it hangs. Every client attached to it is then waiting on the same thing.
Scripts are the other kind of client. Those built on the programmatic client find and connect to the local service on their own, and the report calls that useful for scheduled tasks [7]. Developers can also expose the service to other machines and pair it with external applications [8].
Anomaly published a detailed technical account of the plugin architecture and hot-reloading in September [12], so that part of the design was public well before Monday's post. Release status was murkier. Developers complained about missing release notes even as updates kept shipping [16].
The API redesign is ground-up [9]. We'd expect that to land hardest on projects already built against the old one. Kilo, which Anaconda acquired in July, had already rebuilt its command-line interface and VS Code extension using OpenCode [14]. The OpenCode repository has north of 212,000 stars and almost 30,000 forks [15].
What to watch
- Whether Anomaly's 2.x docs state the default bind address and authentication for a service exposed to other machines.
- Whether 2.x changelog entries arrive with release notes, the gap developers complained about during the beta.
- Whether downstream projects such as Kilo move to the rebuilt API and SDK.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence55
- Adoption70
- Hype gap+20
- Incentives60
- Confidence65
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
OpenCode 2.0 introduces a shared background service connecting its terminal, web and desktop interfaces.
- [2]
Version 2.0 adds a rebuilt API, a new embeddable SDK, and support for running subagents and shell commands in the background.
- [3]
In a blog post published on Monday, Anomaly calls the release a "major overhaul" and says it drew on the experiences of "millions of daily users".
- [4]
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.
- [5]
With version 2.0, the server starts automatically as a single background process on the developer's machine, allowing the terminal, browser and desktop interfaces to communicate with the same underlying service.
- [6]
Developers can access and manage coding sessions through different interfaces while the service handles the underlying execution.
- [7]
Scripts built using OpenCode's programmatic client can automatically discover and connect to the local service, making it useful for scheduled tasks.
- [8]
Developers can additionally expose the service to other machines and pair it with external applications.
- [9]
The architectural changes are accompanied by a ground-up redesign of OpenCode's API.
- [10]
Developers can 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.
- [11]
OpenCode 2.0 was formally unpacked on Monday, some three months after its public beta launch.
- [12]
Anomaly published a detailed technical account of OpenCode's revamped plugin architecture and hot-reloading capabilities in September.
- [13]
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.
- [14]
In July, Anaconda acquired Kilo, an open-source coding agent; Kilo had already rebuilt its command-line interface and VS Code extension using OpenCode.
- [15]
The OpenCode GitHub repository has accumulated north of 212,000 stars and almost 30,000 forks.
- [16]
The drawn-out rollout caused confusion among developers, with questions about whether 2.0 was officially stable and complaints about missing release notes, even as updates kept shipping.
Sources
2 independent publishers whose own reporting we read for this story.
- OpenCode 2.0: A Big Update for the Open Coding Agent
anoma.ly
1 article · October 13, 2026
- thenewstack.io“A major overhaul”: OpenCode 2.0 puts its terminal, desktop, and web apps on one shared service
1 article · October 12, 2026