opencode v2 (2.x) support for @omniroute/opencode-plugin?

[morpheus9393]

Hi, quick roadmap question about @omniroute/opencode-plugin.

Setup: OpenCode (moving to 2.x via OpenChamber 2.0) + OmniRoute gateway (3.8.x, Docker), using the plugin for the live /v1/models catalog and combo routing via /api/combos.

Problem: OpenCode 2.x broke the plugin API (Plugin.define({id, setup}) from @opencode-ai/plugin). The current plugin release (0.2.1) is v1-only and will not load under OC2.

Questions:

1. Is a v2-compatible release of @omniroute/opencode-plugin planned? If yes, is there a rough timeline or a branch/PR to watch?
2. If not (or not soon): is the raw OpenAI-compatible provider entry in opencode.jsonc the officially recommended path going forward — i.e., should we treat the plugin as deprecated for OC2 and wire combos/models statically?

Happy to test a beta/RC against a live 3.8.x gateway and report back. Thanks!

[charleech]

Would the @omniroute/opencode-plugin-v2 mentioned in the OpenCode v2 plugin — Install and Configure help with this issue?

[diegosouzapw]

@morpheus9393 Yes, there is a v2 plugin, and @charleech pointed at the right place. It isn't on npm yet, though, and the guide doesn't say that.

• The code lives in the repo as @omniroute/opencode-plugin-v2. It was added in feat(opencode): opencode v2 plugin publishing the OmniRoute catalog #12870 (09-06) and implements the OC2 define({ id, setup }) contract: catalog, combos, auto-combos and enrichment through catalog.transform, and auth through integration.transform. It's a separate package because v1 and v2 load plugins through different contracts.
• Publishing: npm view @omniroute/opencode-plugin-v2 currently returns 404. The publish-opencode-plugin-v2 job in npm-publish.yml runs when a GitHub release is published, and feat(opencode): opencode v2 plugin publishing the OmniRoute catalog #12870 landed after v3.8.50 shipped, so the first npm release comes with v3.8.51. There's no date for that yet; Any rough ETA for 3.8.51? #14139 is where the ETA gets posted.

To use it today, install it from a checkout. The plugin README covers this under "Local file:// install":

git clone --branch release/v3.8.51 https://github.com/diegosouzapw/OmniRoute
cd "OmniRoute/@omniroute/opencode-plugin-v2" && npm ci && npm run build

{
  "plugins": [
    {
      "package": "file:///path/to/OmniRoute/@omniroute/opencode-plugin-v2",
      "options": { "providerId": "omniroute", "baseURL": "http://localhost:20128" }
    }
  ]
}

Keep the folder's root server.js. OpenCode probes for server.* / index.* at the package root and never reads main/exports, so a folder with only dist/ is skipped silently.

It works against a 3.8.x gateway. The guide (docs/guides/OPENCODE-V2-PLUGIN.md) covers the three places the gateway key can come from, and the separate management token that combos and enrichment need. One migration note from the README: v2 publishes the provider id bare (omniroute/...), not opencode-omniroute/..., so sessions pinned to the old prefix need to re-select the model.

On your second question: the plugin isn't deprecated for OC2. A static OpenAI-compatible provider entry does work, but you give up the live catalog and combos. Your offer to test is very welcome. A report of how the file:// install behaves under OpenChamber 2.0 is exactly what's useful before the npm release.

[diegosouzapw]

@morpheus9393 Update on the v2 plugin, and it's not the news I wanted to give you. v3.8.51 shipped on 2026-09-30 with @omniroute/opencode-plugin-v2 in the tree (@omniroute/opencode-plugin-v2/), but the npm publish of the plugin failed on its first attempt (404 on the PUT, because the package has never been created on npm), so npm install @omniroute/opencode-plugin-v2 still does not work. It's tracked in #15287. The guide says to install from npm, which is wrong until that's fixed.

The file:// install I described earlier still works, and it's the way to use it today, from a checkout of release/v3.8.51 (or the v3.8.51 tag):

git clone --branch v3.8.51 https://github.com/diegosouzapw/OmniRoute
cd "OmniRoute/@omniroute/opencode-plugin-v2" && npm ci && npm run build

Then point opencode.json at file:///path/to/OmniRoute/@omniroute/opencode-plugin-v2, as in the plugin README. Your offer to test it under OpenChamber 2.0 is still the most useful thing right now.

[morpheus9393]

Thank you very much for your effort und letting me know. I already running 3.8.51 with the included v2 plugin via file load and it works very well. Many issues we faced in 3.8.49 have disappeared! Thanks!

[diegosouzapw]

@morpheus9393 @charleech Update: @omniroute/opencode-plugin-v2 is now on npm. Version 0.1.0 was published on 2026-10-18 by the maintainer, under the same account as omniroute (npm view @omniroute/opencode-plugin-v2 shows it, latest is 0.1.0). It was tracked in #15287, which is now closed.

So the file:// workaround from my earlier comments is no longer needed: you can add the package by name in opencode.json (the plugin README has the options, providerId and baseURL). It declares @opencode/plugin >=2.0.12 <3 as a peer dependency. I haven't installed it from npm myself yet, so if the install or the OpenChamber 2.0 test turns up anything, please say so here. The guide (docs/guides/OPENCODE-V2-PLUGIN.md) should now be accurate again.

[diegosouzapw]

Closing for inactivity -- feel free to reopen if you still hit this, or open a fresh issue with a current log. Thanks!