Repository navigation
[FEATURE]: Publish V2 binaries to GitHub Releases so ACP clients can install V2 from the ACP registry #57058
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
ACP clients don't configure agents one by one. JetBrains IDEs, Zed, ACP Patchbay (VS Code) and the rest install agents from the ACP registry: the user picks OpenCode from a list, and the client downloads and runs what the registry entry points at.
The registry's opencode entry is built from this repo's GitHub Releases, and its updater takes the highest stable release with per-platform archives. Those are V1 only (today v1.19.3); V2 ships through opencode.ai, npm and brew. So every registry client runs V1, whichever client it is: IntelliJ in #54133, VS Code in #11176. Both got the same workaround, adding V2 by hand as a custom agent. That fixes one user in one client. It isn't an install path, and every other client needs its own version of it.
The ask: publish V2 releases on GitHub Releases with per-platform archives, the way V1's are (opencode-<os>-<arch>.zip / .tar.gz). The registry's standard updater then picks V2 up with no registry-side code, the same path every other binary agent in the registry uses.
One consequence to decide on your side: because the updater takes the highest stable release, V2 releases here move the opencode entry to V2. If V1 has to stay installable from the registry for a while, say so. agentclientprotocol/registry#657 adds a separate opencode-v2 entry (it reads the opencode.ai feed and is tested on Linux and Windows) and could carry V2 until then. A maintainer's word there would settle which way the registry goes.
Activity
opencode-agent commentedon Oct 19, 2026
Thanks for the detailed write-up! You're asking for V2 releases on GitHub Releases to include per-platform archives, the way V1's do, so the ACP registry's standard updater picks up V2 and clients like JetBrains, Zed and ACP Patchbay stop installing V1. Maintainers will consider it, including whether the registry should move the
opencodeentry to V2 or carry V2 as a separateopencode-v2entry (agentclientprotocol/registry#657) for a while.Related issues and PRs:
hussain commentedon Oct 21, 2026
Update: agentclientprotocol/registry#657 landed, so V2 now installs from the ACP registry as its own
opencode-v2entry (2.1.2 today) in every registry client — IntelliJ, Zed, ACP Patchbay and the rest. That was the point of this issue, so I'm closing it. Which version the mainopencodeentry serves is yours to decide when V1 retires.