You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[v2 Windows] v2.0.3 times out waiting for background service after local CLI install #49034
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
On Windows, install @opencode/cli so it is present under node_modules/@opencode/cli.
From node_modules/@opencode/cli, run:
node .\postinstall.mjs
Confirm the installed v2 CLI:
opencode2 --version
Output:
opencode v2.0.3
Run:
opencode2
It prints Starting background server... and then times out waiting for the background service.
Since you already mention these in your report, it would be worth confirming whether your reproduction matches those issues exactly. If so, adding your details as a comment there (with the v2.0.3 version info) would help consolidate tracking.
Activity
github-actions commentedon Sep 14, 2026
This issue might be a duplicate of existing issues. Please check:
Since you already mention these in your report, it would be worth confirming whether your reproduction matches those issues exactly. If so, adding your details as a comment there (with the v2.0.3 version info) would help consolidate tracking.