September 24, 2026
OpenCode 2 will retain old configs: V1 plugins will need to be ported
On September 23, OpenCode 2 retained V1 configs but stopped running its plugins. Old settings are read without rewriting the file, but plugins must be migrated to the new API.
dax
@thdxr
Making good progress on the OpenCode 2.0 blog post.
· 4K views
Previously, V1 configs and plugins worked as a single unit. Now OpenCode reads existing configs, but a V1 plugin will not work simply by moving the file or renaming the config.
Files change on the fly. A new plugin file runs immediately, while edits and deletions are visible to all sessions. Config, MCP servers, and plugins reload through a unified State mechanism, while the model catalog updates at startup and then once an hour.
Moving to V2. Before installation, the packaged V1 must be removed: both versions use the `opencode` command, and the V2 curl installer replaces the old binary. V2 can be installed via curl, Homebrew, or npm; OpenCode Go costs $10 per month, and you can connect your own provider through `/connect`.
A post on how OpenCode 2 works is still in the works.
Source
