OpenCode provider cannot use an alternate opencode2 binary

[mynameistito]

What happened

T3 Code reports:

OpenCode Unavailable — Failed to execute OpenCode CLI

The machine has OpenCode installed as opencode2, but T3 attempts to execute opencode.

Diagnosis

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

binaryPath: "opencode"

The installed working executable is opencode2. The opencode command resolves to a broken Bun shim and fails with:

bin executable does not exist on disk

T3 then reports that the OpenCode CLI is not installed or not on PATH.

The OpenCode runtime executes the configured binary path directly, so alternate executable names must be configured manually.

Steps to reproduce

1. Install or expose OpenCode 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 or allows the installed OpenCode executable.

Actual: T3 reports that OpenCode is unavailable because it tries to execute opencode.

Version

T3 Code 0.0.40

Environment

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

Evidence

Configured OpenCode binaryPath: opencode
Installed alternate executable: opencode2
OpenCode status: OpenCode CLI (`opencode`) is not installed or not on PATH.
Direct opencode launch: bin executable does not exist on disk

The runtime constructs its error from the configured binary path, so the failure specifically references opencode.

Related issues

No matching issue found. OpenCode configuration-content and server-timeout issues appear related to other failure modes.

Fix applied or workaround

Changed the local OpenCode provider configuration from:

binaryPath: "opencode"

to:

binaryPath: "opencode2"

T3 Code needs to be restarted or the provider status refreshed before verifying the change.

Filed by

GPT-5 via Codex

[juliusmarminge]

Likely addressed by open PR #8207 (feat(server): support OpenCode 2 alongside OpenCode 1), which discovers the opencode2 binary and treats OpenCode 2 as a first-class path. Workaround until that lands: set OpenCode binaryPath to opencode2 (as noted in the report).

[juliusmarminge]

Same OpenCode2 gap as #11036 — tracked by #6961 and open PR #8207.

[juliusmarminge]

Closing as duplicate of the OpenCode V2 track: #6961 — covered by open PR #8207. Sibling of #11036.