Day 7 receipt
OpenCode 2.0
Day 2 of 7The launch post is undated; 14 Oct is when it reached Hacker News. The v2.0.0 git tag dates from 12 Sep and 2.0.x builds were on the 'latest' channel by late September.
A rebuild of the open-source coding agent around a shared background service, a new API, code mode for MCP servers and background subagents.
Launch dayWhat they claimed, quoted word for word · 5
“In 2.0 this server now automatically runs as a single background process on your machine.”
It does, but when it fails it takes every client with it: a migration error stopped the service from starting, and failed MCP connections stay failed until a service restart.
“All MCP servers in 2.0 are opted into code mode by default.”
No solid reports on code mode itself yet.
“First, we've added background subagents.”
No solid reports either way.
“There are a lot of other changes but they are backwards compatible.”
The post lists three breaking changes. Separately, users hit v1-to-v2 data migration failures, including thousands of dropped messages.
“We also spent quite a lot of time ensuring everything in OpenCode 2.0 can be hot-reloaded.”
No solid reports either way.
Day 7What real users report · 8
v2 releases had no published release notes: the changelog stopped at v1 and the v2 changelog page returned 404, so users had to diff tags to see what changed.
Open as of 16 Oct · 31 reactions · Open the source
The v2 TUI sometimes ate 24–28 GB of memory in under a minute and was killed; the reporter never saw this on v1.
Closed as completed · 12 comments · Open the source
The automatic v1-to-v2 migration silently dropped 6,238 older assistant messages across 92 sessions; the reporter recovered them with their own fix.
Closed as not planned · 6 comments · Open the source
After upgrading a long-lived v1 database to 2.0.29, a migration error stopped the background service from starting at all; the same upgrade worked on another machine.
Closed as completed · Open the source
Because MCP state now lives in the background service, a remote MCP server that fails once (for example after sleep) is never retried until the service is restarted.
Open as of 16 Oct · 8 comments · Open the source
On native Windows, the v2 TUI lags on scrolling and window resizing, while the desktop app and the v1 TUI were smooth on the same machine.
Open as of 16 Oct · 6 comments · Open the source
After the 2.0 update, the VS Code extension stopped working because the CLI no longer accepted the flags it used.
Closed as duplicate · Open the source
The launch post drew a large Hacker News discussion.
868 points · 381 comments · Open the source