anomalyco / anomalyco/opencode

[v2 Windows] v2.0.3 times out waiting for background service after local CLI install

Open
#49,034 1 comment 0 reactions 1 assignee View on GitHub

@Hona is already working on this.

Since Sep 14, 2026.

2.0
Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description
Description

On Windows, opencode2 from @opencode/cli v2.0.3 fails to start the managed background service and exits with:

Starting background server...
[07:36:33.937] ERROR (#1): Error: Timed out waiting for the background service to start
    at <anonymous> (B:/~BUN/root/chunk-4e5snr3z.js:3:5676)
    at service.ensure (B:/~BUN/root/chunk-en214e40.js:3:662)
    at service.ensure (definition) (B:/~BUN/root/chunk-4e5snr3z.js:3:3933)
    at cli.server-connection.resolve (B:/~BUN/root/chunk-115pyc4p.js:2780:6687)
    at cli.server-connection.resolve (definition) (B:/~BUN/root/chunk-en214e40.js:2:399)

The package postinstall completes without an error and opencode2 --version reports opencode v2.0.3, but launching opencode2 itself cannot bring up/connect to the background service.

This may be related to #41746 / #41696, but this reproduces on the stable v2.0.3 release rather than an older next build.

Plugins

None required to reproduce; startup fails before the TUI opens.

OpenCode version

opencode v2.0.3

Steps to reproduce
  1. On Windows, install @opencode/cli so it is present under node_modules/@opencode/cli.
  2. From node_modules/@opencode/cli, run:
node .\postinstall.mjs
  1. Confirm the installed v2 CLI:
opencode2 --version

Output:

opencode v2.0.3
  1. Run:
opencode2
  1. It prints Starting background server... and then times out waiting for the background service.
Screenshot and/or share link

No response

Operating System

Windows 11 Pro

Terminal

PowerShell 7.6.5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.