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
Thanks for the report! I tried this on Linux with v2.0.24: I started opencode, quit with Ctrl+C and started it again several times, and the background service came back each time. So this looks specific to Windows, where Ctrl+C is delivered to processes differently. It needs a maintainer with a Windows machine to reproduce it.
In the meantime, these would help:
The exact error text from the screenshot, pasted as text
The output of opencode service status right after it fails
Whether an opencode.exe process is still running in Task Manager at that point, and whether ending it (or running opencode service restart) lets opencode start again
The relevant part of %USERPROFILE%\.local\share\opencode\log\opencode.log around the failure (please remove API keys and other sensitive data)
Whether it also happens after only a short session, or only after a long one
C:\code\copilot-worktrees>opencode2
Error: Background service failed to start
at <anonymous> (B:/~BUN/root/chunk-c0q6gxje.js:3:6220)
at service.ensure (B:/~BUN/root/chunk-ntjmkcr5.js:3:690)
at service.ensure (definition) (B:/~BUN/root/chunk-c0q6gxje.js:3:5105)
at cli.server-connection.resolve (B:/~BUN/root/chunk-33r0xqka.js:96:6565)
at cli.server-connection.resolve (definition) (B:/~BUN/root/chunk-ntjmkcr5.js:2:402)
2
<I don't have output of opencode service status right after it fails>
3
I am using opencode2, not opencode
its at
C:\Program Files\nodejs\opencode2
C:\Program Files\nodejs\opencode2.cmd
opecode2 process was running in Task Manager at that point
4
Relevant part of %USERPROFILE%.local\share\opencode\log\opencode.log
Activity
opencode-agent commentedon Oct 7, 2026
Thanks for the report! I tried this on Linux with v2.0.24: I started
opencode, quit with Ctrl+C and started it again several times, and the background service came back each time. So this looks specific to Windows, where Ctrl+C is delivered to processes differently. It needs a maintainer with a Windows machine to reproduce it.In the meantime, these would help:
opencode service statusright after it failsopencode.exeprocess is still running in Task Manager at that point, and whether ending it (or runningopencode service restart) letsopencodestart again%USERPROFILE%\.local\share\opencode\log\opencode.logaround the failure (please remove API keys and other sensitive data)Related issues, ordered by likelihood:
opencode servewithSTATUS_CONTROL_C_EXIT, and the leftover socket then blocks restartsopencode2times out waiting for the background service to startserve --servicemanoharreddyporeddy commentedon Oct 8, 2026
1
Error text
2
<I don't have output of opencode service status right after it fails>
3
I am using opencode2, not opencode
its at
C:\Program Files\nodejs\opencode2
C:\Program Files\nodejs\opencode2.cmd
4
Relevant part of %USERPROFILE%.local\share\opencode\log\opencode.log
5
Happened after a 1hr+ minute session, although model might be idle most of the time due to inactivity.