Repository navigation
Upgrade version confusion #54813
Description
Description
Last week, my opencode 1.18.0 on one system offered an upgrade to version 2. This week on another system, opencode offered 1.19.0 as the latest to move to, with no version 2. The releases section of opencode's Github page doesn't show a version 2. The issues bot says version 1 won't get any more updates as version 2 is the new version. This is confusing.
Plugins
N/A
OpenCode version
As mentioned
Steps to reproduce
As above
Screenshot and/or share link
No response
Operating System
Ubuntu
Terminal
OS terminal
Activity
opencode-agent commentedon Oct 12, 2026
Thanks for raising this, @huornlmj. The mixed signals are understandable, so here is what is most likely going on.
Both versions you have (1.18.0 and 1.19.0) are OpenCode v1. v2 (2.x) is a separate implementation, published as its own package,
@opencode/cli. That is why there is no 2.x on the GitHub releases page, which still lists v1 releases.v1 looks for updates through whatever installed it, and those sources currently point to different versions:
opencodeformula now points to 2.x. A Homebrew-installed v1 will therefore offer an upgrade to v2.opencode-ai) and the GitHub releases still point to the newest 1.x. A v1 installed that way will offer the next 1.x release, such as 1.19.0.My guess is that the two systems were installed in different ways. You can check with
which opencodeandbrew list opencodeon each.v1 now only gets fixes for critical bugs, so this is unlikely to change on the v1 side. We encourage moving to v2, for example with
npm i -g @opencode/cli. v1 and v2 use different session databases and plugin APIs, so upgrade when it suits you. If you want to stay on v1 for now, set"autoupdate": "notify"(orfalse) in your config and choose Skip in the update dialog. On a Homebrew install, also runbrew pin opencode.Related:
If you think this is a critical problem, or you see something similar on v2, please reply here.
opencode-agent commentedon Oct 13, 2026
Closing this as not planned. Both systems run OpenCode v1 (1.18.0 and 1.19.0), and the different upgrade offers come from v1 checking for updates through its install method. Homebrew's
opencodeformula now points to 2.x, while npmopencode-aiand the GitHub releases still point to 1.x. v1 only gets critical fixes, and we haven't heard that this is critical or that it also happens on v2.To move to v2, install
@opencode/cli(for examplenpm i -g @opencode/cli). To stay on v1, set"autoupdate": "notify"and, on Homebrew, runbrew pin opencode. See #54066 for the related Homebrew upgrade problem.If you see confusing upgrade behaviour on v2, please open a new issue. Thanks, @huornlmj!