anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-23 02:36:57 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Opencode desktop (beta) v1.1.27 fails to install on windows #6954

New Issue
Closed
opened 2026-02-16 18:05:42 -05:00 by yindo · 8 comments
yindo commented 2026-02-16 18:05:42 -05:00
Owner
Copy Link
Copy Source

Originally created by @othaime-en on GitHub (Jan 20, 2026).

Originally assigned to: @adamdotdevin on GitHub.

Description

Hey there. I just (about 30 mins ago) installed opencode desktop for windows and I run into a weird issue.
First, during the installation process, you get this popup error saying

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

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

Plugins

No response

OpenCode version

1.1.27

Steps to reproduce

  1. Download the opencode installer for windows.
  2. Start the installation process.
  3. Midway (after the .exe file is extracted, you get a wierd error saying "Error opening file for writing" I have attached it below.
  4. Click ignore to proceed.
  5. Finish installation and start the app.
  6. You get the error pasted in the description above and the second screen shot below.

Screenshot and/or share link

Image Image

Operating System

Windows 10

Terminal

No response

Originally created by @othaime-en on GitHub (Jan 20, 2026). Originally assigned to: @adamdotdevin on GitHub. ### Description Hey there. I just (about 30 mins ago) installed opencode desktop for windows and I run into a weird issue. First, during the installation process, you get this popup error saying ``` Error: Failed to spawn OpenCode Server. Logs: [STDOUT] opencode server listening on http://127.0.0.1:11055 at castError (http://tauri.localhost/assets/index-4gcs5kzd.js:2:11968) at http://tauri.localhost/assets/index-4gcs5kzd.js:2:4662 ``` ### Plugins _No response_ ### OpenCode version 1.1.27 ### Steps to reproduce 1. Download the opencode installer for windows. 2. Start the installation process. 3. Midway (after the .exe file is extracted, you get a wierd error saying "Error opening file for writing" I have attached it below. 4. Click ignore to proceed. 5. Finish installation and start the app. 6. You get the error pasted in the description above and the second screen shot below. ### Screenshot and/or share link <img width="756" height="576" alt="Image" src="https://github.com/user-attachments/assets/212000bb-6b41-43cd-8837-eea48c7b9e0b" /> <img width="1427" height="745" alt="Image" src="https://github.com/user-attachments/assets/762524d6-8538-4feb-b438-aa02776035ad" /> ### Operating System Windows 10 ### Terminal _No response_
yindo added the windowsbugweb labels 2026-02-16 18:05:42 -05:00
yindo closed this issue 2026-02-16 18:05:42 -05:00
yindo commented 2026-02-16 18:05:43 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 20, 2026):

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

  • #7475: Error: Failed to spawn OpenCode Server (macOS, similar spawn error)
  • #8200: window install error Failed to spawn OpenCode Server (Windows, same error message)
  • #9043: Desktop Can't be installed On Windows10 (Windows installation issue)
  • #5673: Error opening file for writing (Windows, same file writing error during installation)

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 20, 2026): This issue might be a duplicate of existing issues. Please check: - #7475: Error: Failed to spawn OpenCode Server (macOS, similar spawn error) - #8200: window install error Failed to spawn OpenCode Server (Windows, same error message) - #9043: Desktop Can't be installed On Windows10 (Windows installation issue) - #5673: Error opening file for writing (Windows, same file writing error during installation) Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 18:05:43 -05:00
Author
Owner
Copy Link
Copy Source

@TianjinAI commented on GitHub (Jan 20, 2026):

+1

@TianjinAI commented on GitHub (Jan 20, 2026): +1
yindo commented 2026-02-16 18:05:43 -05:00
Author
Owner
Copy Link
Copy Source

@adamdotdevin commented on GitHub (Jan 20, 2026):

You should be able to get it running again if you kill all bun/opencode processes and reinstall. Are you using a proxy?

@adamdotdevin commented on GitHub (Jan 20, 2026): You should be able to get it running again if you kill all bun/opencode processes and reinstall. Are you using a proxy?
yindo commented 2026-02-16 18:05:43 -05:00
Author
Owner
Copy Link
Copy Source

@othaime-en commented on GitHub (Jan 20, 2026):

Oh hey, That worked! I tried it before but I guess I wasn't killing all processes.
I wasn't using a proxy. But I had an idle background process from one of my providers, killed it too. Hard to say which did the trick, the proxy or the bun processes.

@othaime-en commented on GitHub (Jan 20, 2026): Oh hey, That worked! I tried it before but I guess I wasn't killing all processes. I wasn't using a proxy. But I had an idle background process from one of my providers, killed it too. Hard to say which did the trick, the proxy or the bun processes.
yindo commented 2026-02-16 18:05:43 -05:00
Author
Owner
Copy Link
Copy Source

@Brendonovich commented on GitHub (Jan 21, 2026):

@othaime-en I don't suppose you'd know what version of OC you were updating from? Versions older than 1.1.17 (released 13 Jan) aren't guaranteed to kill their opencode-cli.exe processes, my guess is you were updating from a version <= 1.1.16 and there were dangling processes that once killed manually started working again.

@Brendonovich commented on GitHub (Jan 21, 2026): @othaime-en I don't suppose you'd know what version of OC you were updating from? Versions older than 1.1.17 (released 13 Jan) aren't guaranteed to kill their `opencode-cli.exe` processes, my guess is you were updating from a version <= 1.1.16 and there were dangling processes that once killed manually started working again.
yindo commented 2026-02-16 18:05:43 -05:00
Author
Owner
Copy Link
Copy Source

@othaime-en commented on GitHub (Jan 21, 2026):

Hmm... I originally installed it last year, so it was definitely older than v1.1.17. However, I uninstalled it a bunch of times and deleted all program data. Well... except for the bun processes from the terminal version. For the most part, I still stumbled onto the same error. But I guess there were dangling processes because I forgot windows sometimes persists AppData folders or files intentionally for reinstallation convenience or just process locks.

@othaime-en commented on GitHub (Jan 21, 2026): Hmm... I originally installed it last year, so it was definitely older than v1.1.17. However, I uninstalled it a bunch of times and deleted all program data. Well... except for the bun processes from the terminal version. For the most part, I still stumbled onto the same error. But I guess there were dangling processes because I forgot windows sometimes persists AppData folders or files intentionally for reinstallation convenience or just process locks.
yindo commented 2026-02-16 18:05:43 -05:00
Author
Owner
Copy Link
Copy Source

@Brendonovich commented on GitHub (Jan 21, 2026):

Ah ic, sounds like a dangling process from the version of the desktop app you had installed. Zombie Bun processes from older desktop versions had no way of being cleaned up after being orphaned, so I'm guessing they stuck around in the background. Either way things should work properly now, do let us know if you run into the same issue again.

@Brendonovich commented on GitHub (Jan 21, 2026): Ah ic, sounds like a dangling process from the version of the desktop app you had installed. Zombie Bun processes from older desktop versions had no way of being cleaned up after being orphaned, so I'm guessing they stuck around in the background. Either way things should work properly now, do let us know if you run into the same issue again.
yindo commented 2026-02-16 18:05:43 -05:00
Author
Owner
Copy Link
Copy Source

@othaime-en commented on GitHub (Jan 21, 2026):

Oh yeah. Definitely!
Thanks for the help 🙂

@othaime-en commented on GitHub (Jan 21, 2026): Oh yeah. Definitely! Thanks for the help 🙂
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label bug web windows
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#6954
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?