OpenCode2 is rejected by T3's OpenCode version check

[mynameistito]

What happened

T3 Code reports:

OpenCode Unavailable — Failed to execute OpenCode CLI

The machine has OpenCode2 installed as opencode2, but T3 Code reports it as unavailable.

Diagnosis

T3 Code v0.0.40 initially had the OpenCode provider configured with:

binaryPath: "opencode"

The opencode command resolves to a broken Bun shim and fails with:

bin executable does not exist on disk

Changing the configured path to opencode2 makes T3 find and launch the executable, but the OpenCode2 version is 0.0.0-beta-19271. T3's OpenCode integration requires OpenCode 1.14.19 or newer, so the health check rejects OpenCode2 as an invalid/unsupported version.

The OpenCode runtime executes the configured binary path directly and performs a semver health check before loading models. Alternate executable names are not sufficient when the CLI reports an incompatible version.

Steps to reproduce

1. Install OpenCode2 under the executable name opencode2.
2. Run T3 Code v0.0.40 on Windows.
3. Enable OpenCode in Settings > Providers.
4. Leave the binary path as the default opencode.
5. Refresh provider status or start an OpenCode thread.

Expected: T3 detects and allows the installed compatible OpenCode executable.

Actual: T3 either reports opencode as missing, or rejects opencode2 because its reported version is below the required OpenCode version.

Version

T3 Code 0.0.40

Environment

Windows win32 x64 build 10.0.26200, Node v24.18.0, desktop app

Evidence

Original configured OpenCode binaryPath: opencode
Tested configured binaryPath: opencode2
opencode --version: bin executable does not exist on disk
opencode2 --version: opencode2 v0.0.0-beta-19271
OpenCode status after switching to opencode2: Unable to determine OpenCode version from `opencode --version` output.

The runtime requires OpenCode v1.14.19 or newer. OpenCode2's 0.0.0-beta-19271 version does not satisfy that requirement.

The attached screenshot shows the desktop provider row still displaying Not found · OpenCode CLI ('opencode') is not... after the local configuration was changed to opencode2, indicating that the running UI/server snapshot had not reloaded the setting.

Related issues

No matching issue found. Existing OpenCode configuration-content and server-timeout issues cover different failure modes. This report concerns OpenCode2 compatibility and version validation.

Fix attempted or workaround

Changed the local OpenCode provider configuration from:

binaryPath: "opencode"

to:

binaryPath: "opencode2"

The persisted settings file was changed from opencode to opencode2, and the T3 server was restarted. T3 then detected the executable but rejected its 0.0.0-beta-19271 version because T3 requires OpenCode 1.14.19 or newer.

No working workaround was found for OpenCode2. A supported OpenCode 1.x installation is required unless T3 adds explicit OpenCode2 support.

Screenshots: the reporter should drag the supplied screenshot into the issue after creation.

Filed by

GPT-5 via Codex

[juliusmarminge]

Tracked by open PR #8207 (OpenCode 2 / opencode2 discovery + preview version support). Same gap as #6961.

[juliusmarminge]

Closing as duplicate of the OpenCode V2 track: #6961 — covered by open PR #8207 (opencode2 discovery + preview version bypass).

[mynameistito]

Tracked by open PR #8207 (OpenCode 2 / opencode2 discovery + preview version support). Same gap as #6961.

opencode didn't fix it but the direct path to it $HOME\\.cache\\.bun\\opencode2.exe

· Failed to execute OpenCode CLI health check: Unable to determine OpenCode version from `opencode --version` output. T3 Code requires OpenCode v1.14.19 or newer.

Prior with just opencode2

· OpenCode CLI (`opencode`) is not installed or not on PATH.

@juliusmarminge