Windows Support

[thdxr]

our windows support isn't really there - creating this one super issue to track all problems

[xmintec]

here is how it works for me

1. Install Chocolatey
   Open PowerShell as administrator.
   Run the following command to relax the execution policy so the installation script can run:

Set-ExecutionPolicy Bypass -Scope Process -Force

Now run the official Chocolatey installation command:

[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))

2. Install the missing tools with Chocolatey:

choco install unzip ripgrep fzf -y

3. Navigate to the folder containing your opencode.exe.
   Double-click and Opencode should run.

[ikifar2012]

here is how it works for me

1. Install Chocolatey
   Open PowerShell as administrator.
   Run the following command to relax the execution policy so the installation script can run:

Set-ExecutionPolicy Bypass -Scope Process -Force

Now run the official Chocolatey installation command:

[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))

2. Install the missing tools with Chocolatey:

choco install unzip ripgrep fzf -y

3. Navigate to the folder containing your opencode.exe.
   Double-click and Opencode should run.

Ideally though I think it would be best if this was bundled into the exe but if not possible then just document this

[davidanew]

I have done this:

choco install unzip ripgrep fzf -y

I updated to the latest version v0.1.189

I still get the "no text" probem , issue #460

[xmintec]

I have done this:

choco install unzip ripgrep fzf -y

I updated to the latest version v0.1.189

I still get the "no text" probem , issue #460

You're right, you can't enter text. Unfortunately, I didn't test it any further than I left the welcome text from Opencode, which was fine for me because I had other things to do. It's the dependency on Bun that's a problem. I've now solved it for myself with Docker, but it's a bit of a hassle. Sooner or later, I'll install it on my Mac; it should work better there.

[davidanew]

For the "bun" problem:

● Here's the problematic macro import on line 5:

import { data } from "./models-macro" with { type: "macro" }

This is a Bun-specific macro import that executes the data() function at compile time to fetch model information from https://models.dev/api.json. The macro system is causing the crash on Windows.

To temporarily fix this, you can comment out that line:

// import { data } from "./models-macro" with { type: "macro" }

The macro is used to embed AI model data at build time, but the application should still work without it (though some model information might not be available).

This worked for me to get the opencode gui up. It still has the "no text" problem, but at least I can starting investigating it

[davidanew]

Setting "Use the legacy input encoding" in Poweshell settings -> Terminal emulation fixes the text problems

[davidanew]

I had a git hash related error when doing /init . This fixed it:

Update(packages/opencode/src/snapshot/index.ts)
⎿  Updated packages/opencode/src/snapshot/index.ts with 20 additions and 2 removals
46 log.info("commit")
47
48 // Extract commit hash from output like "[main abc1234] snapshot"
49 - const match = result.stdout.toString().match(/[.+ ([a-f0-9]+)]/)
50 - if (!match) throw new Error("Failed to extract commit hash")
49 + const output = result.stdout.toString()
50 + log.info("git commit output", { output, stderr: result.stderr.toString() })
51 +
52 + const match = output.match(/[.+ ([a-f0-9]+)]/)
53 + if (!match) {
54 + // Fallback: get commit hash with git rev-parse
55 + try {
56 + const hashResult = await $git --git-dir ${git} rev-parse HEAD
57 + .quiet()
58 + .cwd(app.path.cwd)
59 + .nothrow()
60 + const hash = hashResult.stdout.toString().trim()
61 + if (hash && hash.length >= 7) {
62 + return hash.substring(0, 7)
63 + }
64 + } catch (e) {
65 + log.error("Failed to get commit hash with rev-parse", { error: e })
66 + }
67 + throw new Error(Failed to extract commit hash from: ${output})
68 + }
69 return match[1]

[strager]

"No text" issues might be related to num lock (see charmbracelet/x#485). Can you try turning off num lock?

[strager]

See also #143

[QDaed]

#404 This issue still remain with the lastest patch