Repository navigation
opencode v2 #3622
Replies: 1 comment
|
Partly. I upgraded OpenCode 1.9 -> 2.0.32 with the ECC .opencode setup, so here is what carried over and what didn't (Windows 10, ECC 2.2.2). Works unchanged: opencode.json with agents, commands, skills paths, instructions and an MCP server. V2 reads the V1 config format. Does not work: the V1 plugin code (.opencode/plugins/ecc-hooks.ts, index.ts, lib/). OpenCode 2.0 refuses to load it ("3 plugins failed"). The V2 migration guide says V1 plugin implementations don't run and need porting to the new API (Plugin.define + setup(ctx), imported from @opencode/plugin): https://opencode.ai/v2/docs/build/plugins/migrate-v1 Port: I rewrote ecc-hooks for the V2 API and tested it: https://gist.github.com/jima05/49b57f84a207df01a3a26353d98cc50d Upgrade gotcha: if you get "API key has expired" after upgrading, an old saved key in the OpenCode data folder may be the cause. Re-sign-in with The port was written with AI assistance (Claude) and tested by hand. Maintainers, feel free to use, change or replace it. Would you want a separate V2 entry point or a dual export? https://gist.github.com/jima05/49b57f84a207df01a3a26353d98cc50d |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
opencode v2 support this old v1 set up ?
All reactions