Repository navigation
Add OpenCode V2 as a separate opt-in binary agent - #657
Conversation
|
Patchbay, an ACP client for VS Code, has a user asking for OpenCode 2 (anomalyco/opencode#11176), so we tested this branch at
Notes: cc @EugeneTheDev, since this is the second user of the |
|
One more data point for review, on the JetBrains side: anomalyco/opencode#54133 reports IntelliJ's OpenCode agent failing at launch for users who have OpenCode 2 installed. The |
|
Asked OpenCode to publish V2 on GitHub Releases, which would let the standard updater carry it, and to say whether V1 must stay listed meanwhile: anomalyco/opencode#57058. |
EugeneTheDev
left a comment
There was a problem hiding this comment.
Thanks, one small verification nit, please take a look
|
Thanks @EugeneTheDev. This unblocked OpenCode V2 across the registry at once: IntelliJ, Zed and ACP Patchbay users now install it in one click instead of writing a custom agent by hand. |
OpenCode 2 has ACP support and official standalone binaries, but the existing registry entry distributes OpenCode 1.18.34 from GitHub Releases. Add a separate
opencode-v2entry named OpenCode V2, allowing users to opt into the major upgrade. The existingopencodeentry and its GitHub-based update behavior are unchanged.The new entry pins v2.0.23 archives and official SHA-256 checksums for macOS, Linux, and Windows on arm64/x64. It copies the existing OpenCode icon and launches native
opencode acpdirectly, without Node.js/npm installation. Windows targets use./opencode.exe.Register a custom stable updater only for
opencode-v2, using https://opencode.ai/update/api/latest/cli/opencode. Future updates refresh URLs and checksums together through the existing custom-source mechanism. Reject incomplete platform sets, prerelease versions, mismatched URLs, and invalid checksums.Migration caveat: separate registry entries isolate installation, not OpenCode configuration. V1 and V2 use the same configuration locations; converting settings to V2-only syntax can affect V1. V1 plugins require porting, server API integrations require migration, and V2 no longer supplies OpenCode LSP tools/diagnostics. See https://opencode.ai/v2/docs/migrate-v1/. ACP setup: https://opencode.ai/v2/docs/cli/acp/.
Validation:
opencode,opencode-v2: both up to date, no errors.opencode-v2entry passes the standalone-binary authentication handshake and reports v2.0.23 andopencode-login(terminal). session/new, session/list, and session/resume succeed. session/fork rejects the empty test session; legacy session/stop and session/set_model are absent (V2 uses session/cancel and config-option controls).opencode/agent.jsonoropencode/icon.svgagainst upstream main.Docker validation was attempted but the local daemon was unavailable, so repository scripts ran natively with isolated agent state. Windows/Linux archives were inspected but not executed. No authenticated model prompt or full Zed UI coding task was tested.