opencode 2.0 ，Windows WSL下，卡住了。并且另外的终端启动报错 #55033

Activity

1. opencode-agent commented on Oct 13, 2026

   

   opencode-agentBot

   on Oct 13, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the report! To work out what's going on, could you please provide:

   1. The exact version: the output of opencode --version.
   2. What the first session was doing when it froze, e.g. stuck on Starting background server... or frozen in the middle of a reply. The screenshot didn't load for us, so please paste the text or attach a PNG. Is the project directory very large (lots of files, or a big git repository)?
   3. The output of opencode service status.
   4. The real startup error. With other opencode instances stopped, run opencode serve --service and paste its output. If a port conflict is the cause, this usually prints something like Managed service port 49374 ... is already in use.
   5. Whether port 49374 is taken: ss -ltnp | grep 49374 (or lsof -i :49374), and whether any old opencode processes are still running (ps aux | grep opencode).

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

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

   • service: hardcoded default port 49374 with no fallback and a silent hang when it's unavailable #52234: on WSL2 the default service port 49374 can be unavailable (e.g. reserved by Hyper-V), and opencode then hangs instead of showing the bind error
   • service: relaunch fails with "Managed service port already in use" when previous background service has not exited #54267: relaunching fails because a previous background service process is still holding port 49374
   • service: hardcoded default port 49374 locks out any second client on shared loopback (multi-user/WSL mirrored), surfacing only a generic timeout #50672: the fixed port 49374 blocks a second client on WSL mirrored networking, with only a generic error shown
   • service: 100% CPU hang when snapshotting a very large git worktree #50734: on WSL the background service hangs at 100% CPU in a very large git worktree, and later starts keep resuming the session and hanging again
   • opencode2 became stuck starting its managed background server #41696 / cli: service discovery intermittently times out waiting for the background service #52021: the background service gets stuck starting, or the CLI times out waiting for it
2. opencode-agent

   added

   triaging

   on Oct 13, 2026
3. Underworldbros commented on Oct 14, 2026

   

   Underworldbros

   on Oct 14, 2026

   Last edited by Underworldbros

   More actions

   Additional WSL2 troubleshooting result — OpenCode v2.0.28

   I encountered repeated managed-service restarts under WSL2, including:

   • Background service is unresponsive
   • Server process ... is still running
   • Managed service port 49374 already in use
   • Repeated HTTP 503 responses from /api/info and /api/model
   • Event-stream connection timeouts and stalls

   Environment: WSL2 Ubuntu, kernel 6.18.40.1-microsoft-standard-WSL2, Node.js v24.13.0, npm-installed @opencode/cli v2.0.28.

   My OpenCode SQLite database was approximately 3.99 GB, with a 163 MB WAL file. I observed a server process blocked in a kernel file-read path while accessing opencode.db. Later, Docker's dockerd process was also in uninterruptible sleep (D state), waiting at submit_bio_wait.

   Observed recovery: OpenCode eventually displayed its “What's New” page, but the Agents list was initially blank and the managed service continued restarting. I then changed to my actual project directory and reopened OpenCode. It opened immediately, and the Agents list populated.

   I have not established that changing directories caused the recovery; the service may have finished initializing at the same time. Nevertheless, reopening from the project directory is a useful troubleshooting observation.

   I have not deleted the database, WAL, or SHM files, and have not run database repair or VACUUM.
4. opencode-agent commented on Oct 16, 2026

   

   opencode-agentBot

   on Oct 16, 2026 – with OpenCode Agent

   Contributor

   More actions

   Closing this for now, since we didn't get the details we need to look into it: the exact opencode --version, what the first session was doing when it froze (the WebP screenshot didn't load for us), and the real startup error from opencode serve --service / opencode service status. Background service failed to start is a generic message, so without those we can't tell what caused it.

   If it still happens, please reply here with that information and we can reopen it. In the meantime, these issues cover similar background-service problems on WSL and may help:

   • service: hardcoded default port 49374 with no fallback and a silent hang when it's unavailable #52234: default service port 49374 unavailable on WSL2
   • service: relaunch fails with "Managed service port already in use" when previous background service has not exited #54267: a previous service process still holding the port
   • service: 100% CPU hang when snapshotting a very large git worktree #50734: the service hanging in a very large git worktree on WSL
5. opencode-agent

   closed this as not plannedon Oct 16, 2026