How to install OpenCode easily on Windows

[weroperking]

Problem

After installing opencode-ai globally on Windows via npm, the opencode command does not work out of the box.

In PowerShell

opencode
# => & : The term '/bin/sh.exe' is not recognized ...

• The auto-generated opencode.ps1 wrapper tries to call /bin/sh.exe, which doesn’t exist on Windows.

In Git Bash

opencode
# => cannot execute binary file

• bin/opencode is a Unix shell script, so Git Bash tries to run it as a Linux binary.
• But the package already bundles a valid Windows binary:

  node_modules/opencode-ai/node_modules/opencode-windows-x64/bin/opencode.exe
  

---

Root Cause

• The npm wrapper (opencode.ps1) assumes a Unix shell (/bin/sh).
• On Windows, this path is invalid, so the wrapper fails.
• Git Bash also fails because it doesn’t know to call the .exe.

---

Workarounds

1. Run the binary directly

   & "C:\Users\<User>\AppData\Roaming\npm\node_modules\opencode-ai\node_modules\opencode-windows-x64\bin\opencode.exe"

2. Patch the wrapper script (opencode.ps1) manually
   Replace:

   & "/bin/sh$exe" "$basedir/node_modules/opencode-ai/bin/opencode" $args

   With:

   & "$basedir/node_modules/opencode-ai/node_modules/opencode-windows-x64/bin/opencode.exe" $args

---

Feature Request

Please update the npm installation process so that:

• On Windows, the wrapper calls the bundled .exe instead of /bin/sh.
• This would allow opencode to run out of the box in PowerShell and Git Bash without manual editing.

---

⚡ This would make installation seamless for Windows developers and avoid the confusion around /bin/sh.exe and cannot execute binary file.

[github-actions]

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

• Windows Support #631: General Windows support tracking issue
• Opencode CLI won't install - Win11 Pro NVM for Windows, Node 24.5.0 x64 - Permission Errors #1945: Similar npm installation failures on Windows with symlink permission errors

The core problem described (PowerShell wrapper calling /bin/sh.exe and Git Bash unable to execute Unix shell scripts) appears to be part of the broader Windows installation issues already being tracked.

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

[rekram1-node]

we should definitely fix that

[VictorZakharov]

Needs to be easier, or it won't take off.

[weroperking]

Needs to be easier, or it won't take off.

Like how ?

[weroperking]

Needs to be easier, or it won't take off.

Anyway, i got another problem after the setup, I don't know if it happend to someone else

The LLM model wwritesthe code nnormally but no files aappearin the directory, do you have any idea

[VictorZakharov]

Installation on Windows should be 1 command + register on LLM like Claude. It should not be more complex than Claude Code itself. While it is more complex, Windows users will use other tools. I'm a software architect.

[weroperking]

Installation on Windows should be 1 command + register on LLM like Claude. It should not be more complex than Claude Code itself. While it is more complex, Windows users will use other tools. I'm a software architect.

Actually I am installing Crush CLI , cuz I got a problems with Opencode , except the installation the agents don't event work properly.

[itsrainingmani]

we should definitely fix that

I have a PR open to address this issue - #2419

[rekram1-node]

@itsrainingmani I saw that, I sent it to Dax to review

[rekram1-node]

I just added him as a reviewer too, but I dmed it to him yesterday

[itsrainingmani]

Thanks! We could probably also update the installation documentation to include Chocolatey, Scoop and WinGet as alternative installation options for Windows. I can make a PR for that.

[rekram1-node]

Closing since npm install was addressed by: #2419

[vec715]

installation via npm still does not work on windows