unable to launch the opencode cli after latest update 2.2.4 #60667

Activity

1. opencodejr commented on Oct 30, 2026

   

   opencodejrBot

   on Oct 30, 2026

   Contributor

   More actions

   Thanks for the report! Background service failed to start is a generic message: the background service started, but its own startup failed, and the actual cause isn't shown in this output. Could you share:

   1. The service log: the most recent lines from %USERPROFILE%\.local\share\opencode\log\opencode.log from around the failed launch, especially any line containing background service boot failed. Please remove anything sensitive first.
   2. The output of running the service in the foreground, which usually shows the underlying error directly:

      opencode service stop
      opencode serve --service --print-logs --log-level debug

   3. How you installed and updated OpenCode: npm, bun, the installer or Desktop, and whether the update to 2.2.4 came from /update, an automatic update or a manual reinstall. Also, do you run OpenCode Desktop on the same machine?

   If you'd like to try something in the meantime: in a similar report, running opencode service stop (or ending any leftover opencode processes in Task Manager) and then launching opencode again got it working.

   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 you're done.

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

   • desktop: service stuck at 500 after SQLite "disk I/O error" on resume from sleep #59189: on Windows, the background service boot fails with SQLiteError: disk I/O error, and the failed process stays on the service port, so every later launch shows Background service failed to start
   • Windows: Running /update leaves background service in a zombie state with "SQLiteError: disk I/O error" causing "Background service failed to start" #59940: the same error and stack trace on Windows right after updating via /update (closed as a duplicate of desktop: service stuck at 500 after SQLite "disk I/O error" on resume from sleep #59189)
   • Starting background server... Error: Background service failed to start #57032: the same message, caused there by an EPERM error when the service tightens permissions on opencode.db
   • service: relaunch fails with "Managed service port already in use" when previous background service has not exited #54267: relaunch fails because an earlier background service is still holding the port
2. opencodejr

   added

   triaging

   on Oct 30, 2026
3. thermeng commented on Oct 30, 2026

   

   thermeng

   on Oct 30, 2026

   Author

   More actions

   updated via /update not opencode update
4. thermeng commented on Oct 30, 2026

   

   thermeng

   on Oct 30, 2026

   Author

   More actions

   it works after opencode service stop
   closing the issue, thanks
5. thermeng

   closed this as completedon Oct 30, 2026
6. opencodejr

   closed this as not plannedon Nov 2, 2026
7. opencodejr commented on Nov 2, 2026

   

   opencodejrBot

   on Nov 2, 2026

   Contributor

   More actions

   We haven't heard back, so I'm closing this for now. Background service failed to start is a generic message, and without the service log we can't tell which of the known causes this is, or reproduce it.

   If you're still stuck, try running opencode service stop, or end any leftover opencode processes in Task Manager, then launch opencode again. If that doesn't help, please comment here with the background service boot failed line from %USERPROFILE%\.local\share\opencode\log\opencode.log, or the output of opencode serve --service --print-logs --log-level debug, and we can reopen this.

   The most likely match is #59189, a Windows boot failure with SQLiteError: disk I/O error that leaves the failed service holding the port. You can follow it for updates. Thanks for the report, @thermeng!