Error: Failed to spawn OpenCode Server.

[Analyst1981]

Question

Error: Failed to spawn OpenCode Server. Logs:
[STDOUT] opencode server listening on http://127.0.0.1:49328

at castError (http://tauri.localhost/assets/index-DT7g4zby.js:2:11968)
at http://tauri.localhost/assets/index-DT7g4zby.js:2:4662

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Error: Failed to spawn OpenCode Server. #7475: Same error message - 'Error: Failed to spawn OpenCode Server.' (also reported on macOS)
• window install error Failed to spawn OpenCode Server #8200: Identical error on Windows - 'Failed to spawn OpenCode Server' with same stack trace
• Desktop App Failing to Start server on Windows #8149: Desktop App Failing to Start server on Windows with similar spawn error

Feel free to ignore if your specific case differs from these.

[NeverMore93]

same issue

[ZeroDegree0d]

Error: Failed to spawn OpenCode Server. Logs:
[STDOUT] opencode server listening on http://127.0.0.1:52028

zu@tauri://localhost/assets/index-CaHlS8ng.js:2:11977
@tauri://localhost/assets/index-CaHlS8ng.js:2:4664

[neocody]

Same issue

[dream1cast]

same issue

[johnsonsleo]

same issue, with Mac 1.1.21 desktop version

[qyi71]

同样的问题，Mac 1.1.21 桌面版也存在此问题。

did you install omo? after I uninstalled omo, openCode worked fine.

[neocody]

having OMO installed lets you re-authorize Claude subscription accounts (no one seems to know why), so I’m not willing to uninstall it just to get the OpenCode app working. Especially since OpenCode worked fine before with OMO installed.

[johnsonsleo]

同样的问题，Mac 1.1.21 桌面版也存在此问题。

did you install omo? after I uninstalled omo, openCode worked fine.

Yea, I re-auth antigravity account then restart OSX and it seems working fine now, bizarrd...

[sixyang]

same issue

[sixyang]

I found the problem, there is something wrong with my network, try ping 127.0.0.1, if it doesn't work, use claude to fix it! Because computer doesn't know where is 127.0.0.1, so it can not connect to the server.

[lcq7748]

same issue

[adamdotdevin]

@NeverMore93 @Analyst1981 @ZeroDegree0d @neocody @lcq7748 @sixyang @johnsonsleo @dream1cast @qyi71 can you upgrade to latest (1.1.64) and let me know if this is resolved?