Infinite "Restarting service.." for OC v2 (on Windows) #57864

Activity

1. opencode-agent commented on Oct 21, 2026

   

   opencode-agentBot

   on Oct 21, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for reporting this, @gimlichael. The "Restarting service…" screen means the TUI can't reach its background service (opencode serve --service), so we need to know why that service doesn't come back after sleep. Next time it happens, could you send the following before you restart your machine?

   1. Logs: the newest files from %USERPROFILE%\.local\share\opencode\log (press WIN+R and paste that path), covering the time around the resume from sleep. Look for lines like Background service is unresponsive, Event stream stalled or already in use.
   2. Service state: in another PowerShell window, the output of opencode service status. Then tell us whether opencode service restart, or opencode service stop followed by starting opencode again, gets you working without a reboot.
   3. Port state: if it still doesn't recover, the output of Get-Process opencode* and netstat -ano | findstr LISTENING, plus the service port shown by opencode service status. This tells us whether the port is still held after the processes have exited.
   4. Environment: how you installed OpenCode (npm @opencode/cli, installer, etc.), and whether you use a VPN, proxy (HTTP_PROXY/HTTPS_PROXY), or firewall/endpoint security software that might reconnect when the machine wakes.

   You can reply here with the details, or edit the issue. If you edit it, please also leave a short comment saying you've updated it so we know you're done.

   These existing issues might be related, ordered from most to least likely. Please check whether one of them already describes your problem:

   • service: recovery loop spawns unbounded serve processes when service becomes unresponsive #57038: on Windows, the background service stops answering while TCP connections still succeed, and recovery keeps spawning new service processes with "port already in use" errors
   • [service]: managed service stalls, watchdog recovery loses sessions (404 "session not found"), restart stampede races the service slot (2.0.25 vs 2.0.26) #54181: the service stalls because the OS stops completing connections to its local port; only an OS-level reset helps
   • client: event stream loops forever and TUI shows "Restarting service…" when HTTP proxy is set without no_proxy #52054: the same endless "Restarting service…" screen, caused by an HTTP proxy routing local traffic without no_proxy (includes a Windows report in the comments)
   • Windows: orphaned LISTENING socket after opencode serve termination (EADDRINUSE until reboot) #57723: on Windows, an orphaned listening socket keeps the port bound until reboot (reported on v1, but the symptom is similar)
2. opencode-agent

   added

   triaging

   on Oct 21, 2026
3. gimlichael commented on Oct 21, 2026

   

   gimlichael

   on Oct 21, 2026

   Author

   More actions

   Just confirmed that opencode service restart works as a workaround.
4. opencode-agent

   closed this as not plannedon Oct 24, 2026
5. opencode-agent commented on Oct 24, 2026

   

   opencode-agentBot

   on Oct 24, 2026 – with OpenCode Agent

   Contributor

   More actions

   We're closing this for now because we haven't heard back with the details we asked for. Without the logs from %USERPROFILE%\.local\share\opencode\log from around the resume from sleep, and the output of opencode service status, we can't tell why the background service doesn't come back, or whether this is the same as #57038, #54181 or #52054.

   If it happens again, please reply here with those details, and say whether opencode service restart or opencode service stop gets you working without a reboot. We can reopen the issue then. Thanks, @gimlichael!