cant start it after new update #55978

Activity

1. opencode-agent commented on Oct 16, 2026

   

   opencode-agentBot

   on Oct 16, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the report! The message Background service failed to start means the background service did start, but something went wrong while it was booting. The actual error is written to the service log rather than shown in the terminal, so we need a bit more to find the cause:

   1. The log: open %USERPROFILE%\.local\share\opencode\log\opencode.log (press WIN+R and paste %USERPROFILE%\.local\share\opencode\log). Please paste the lines from around the failed start, especially any ERROR lines or stack traces from the service. Remove anything private first.
   2. A restart: does running opencode service restart and then opencode again fix it? Please paste the output of opencode service status and opencode --version too.
   3. Your setup: how did you install OpenCode (npm, installer, scoop, …)? Do you have a global opencode.json/config, plugins or MCP servers configured? Are HTTP_PROXY/HTTPS_PROXY set, or is WSL running?

   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 issues look related but show different errors. They're ordered from most to least likely, in case one of them already covers your problem:

   • Opencode TUI cannot be started with opencode v2 #55973: v2 fails to start with "Server process exited with code 1"; the cause was an HTTP proxy set without NO_PROXY=127.0.0.1
   • Windows CLI: WSL2 镜像网络预留范围内的 45278 导致服务启动失败，端口查询无占用记录 #55918: Windows 2.0.30 background service can't use its default port because WSL2 mirrored networking reserves it
   • desktop: background service spawn fails "port in use" on Windows/WSL2 mirrored networking — app stuck at logo, error not logged #55907: Windows desktop app's background service won't start under WSL2 mirrored networking
   • service: relaunch fails with "Managed service port already in use" when previous background service has not exited #54267: relaunching fails because the previous background service hasn't exited yet
2. opencode-agent

   added

   triaging

   on Oct 16, 2026
3. karmaMGL commented on Oct 16, 2026

   

   karmaMGL

   on Oct 16, 2026

   Author

   More actions

   1. 2026-10-16T06:20:46.594Z ERROR background service boot failed Cause([Die(SQLiteError: disk I/O error)])
      2026-10-16T06:20:47.303Z ERROR cli process failed Cause([Fail(Error: Background service failed to start)])

   2. yes restarting the service did worked thx

   3. no proxy i have blender mcp and unity doesnt really work or not really good at it
      thx
4. karmaMGL

   closed this as completedon Oct 16, 2026
5. opencode-agent commented on Oct 16, 2026

   

   opencode-agentBot

   on Oct 16, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the log line and for checking the restart, that's exactly what we needed. 🙏

   SQLiteError: disk I/O error during service startup is a problem we already know about. I think this is a duplicate of #55107. The error itself is usually short-lived; on Windows it often happens around an update, while something else still has the database files open. The real problem is what happens next. The service process that failed to boot doesn't exit and stays registered, so every later opencode launch shows Background service failed to start, even after the disk error has gone. That's why opencode service restart fixed it for you.

   Related issues, ordered from most to least likely to be the same problem:

   • Updates #55107: same SQLiteError: disk I/O error during service boot, after which every launch fails until the service is restarted
   • opecode v2 fails to restart after Ctrl + C #53782: the same Background service failed to start on Windows 11 after quitting with Ctrl+C
   • fix(client): stop failed services before reporting startup errors #55311: open pull request that stops a service that failed to boot, so the next launch recovers by itself

   If it happens again, opencode service restart is the workaround. The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different.
6. opencode-agent

   added

   pending close

   on Oct 16, 2026
7. opencode-agent

   closed this as duplicateon Oct 17, 2026
8. opencode-agent commented on Oct 17, 2026

   

   opencode-agentBot

   on Oct 17, 2026 – with OpenCode Agent

   Contributor

   More actions

   Closing this as a duplicate of #55107. It's the same SQLiteError: disk I/O error during service startup, after which the failed service stays registered and every launch shows Background service failed to start. Please follow #55107 for updates; pull request #55311 is open to fix it, so the next launch recovers by itself. Until then, opencode service restart gets you running again. Thanks for sending the log line, @karmaMGL! If you see this again and restarting doesn't fix it, please comment here or open a new issue with the log.