Skip to content

[Bug]: Failed to execute OpenCode CLI health check #2337

Description

@aladicf

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

  1. Downloaded the newest OpenCode on my Windows machine.
  2. Subscribed to OpenCode Go plan.
  3. Connected the CLI to my API Key and tested if it works, it did.
  4. Opened newest nightly version of T3Code(i also tried latest stable) and saw an error message under OpenCode Section in T3Code Settings.

Expected behavior

Expected it to give the same message/notice as it does under Codex section.
Authenticated - Plan name

Actual behavior

Got this message instead.

OpenCode
v1.14.24
Unavailable - Failed to execute OpenCode CLI health check: Timed out waiting for OpenCode server start after 5000ms.

Impact

Blocks work completely

Version or commit

No response

Environment

Windows 10 / Newest Nightly and Stable T3Code / Node 25.9.0 / Bun 1.3.13 / OpenCode 1.14.24

Logs or stack traces

Screenshots, recordings, or supporting files

Screenshot_1.png
Screenshot_2.png

Workaround

No response

Activity

  1. added
    bugSomething is broken or behaving incorrectly.
    needs-triageIssue needs maintainer review and initial categorization.
    on Apr 24, 2026
  2. ssswagatss commented on Apr 27, 2026

    @ssswagatss
    Image Image

    The settings could figure out the Opencode Version, But complains "Not found - OpenCode CLI (opencode) is not installed or not on PATH."

  3. adammansfield commented on Apr 27, 2026

    @adammansfield
    Contributor

    Did you install opencode with npm i -g opencode-ai? If you did, then this is a duplicate of #2163 with a proposed fix in #2183.

    Try running the following and check if you see opencode.cmd to confirm:

    where.exe opencode
    # C:\Program Files\nodejs\opencode
    # C:\Program Files\nodejs\opencode.cmd
  4. aladicf commented on Apr 27, 2026

    @aladicf
    Author

    Did you install opencode with npm i -g opencode-ai? If you did, then this is a duplicate of #2163 with a proposed fix in #2183.

    Try running the following and check if you see opencode.cmd to confirm:

    where.exe opencode
    # C:\Program Files\nodejs\opencode
    # C:\Program Files\nodejs\opencode.cmd

    that doesnt have anything to do with my issue.. he commented a different issue on mine..

  5. AJ-505 commented on Jun 21, 2026

    @AJ-505

    More info concerning this:

    In my experience, if you spin up the Opencode server (opencode web) yourself and configure T3Code settings to hook up with the server manually, the issue does not persist and the Opencode provider works well on T3Code in that situation.

    This has been my workaround for many weeks now.

  6. juliusmarminge commented on Jul 20, 2026

    @juliusmarminge
    Member

    Closing as fixed for the reported five-second OpenCode startup failure by merged PR #4132, which raises the health-check deadline to 30 seconds. Please file a fresh report with current logs if bundled local launch still fails for another cause.

  7. removed
    needs-triageIssue needs maintainer review and initial categorization.
    on Jul 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or behaving incorrectly.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions