Windows Support #456

@xmintec commented on GitHub (Jul 3, 2025):

here is how it works for me

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'))

Install the missing tools with Chocolatey:

choco install unzip ripgrep fzf -y

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

@xmintec commented on GitHub (Jul 3, 2025): 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.

yindo commented

@ikifar2012 commented on GitHub (Jul 3, 2025):

here is how it works for me

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'))

Install the missing tools with Chocolatey:

choco install unzip ripgrep fzf -y

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

@ikifar2012 commented on GitHub (Jul 3, 2025): > 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

yindo commented

@davidanew commented on GitHub (Jul 4, 2025):

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

@davidanew commented on GitHub (Jul 4, 2025): 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

yindo commented

@xmintec commented on GitHub (Jul 4, 2025):

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.

@xmintec commented on GitHub (Jul 4, 2025): > 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](https://github.com/sst/opencode/issues/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.

yindo commented

@davidanew commented on GitHub (Jul 4, 2025):

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 commented on GitHub (Jul 4, 2025): 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

yindo commented

@davidanew commented on GitHub (Jul 4, 2025):

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

@davidanew commented on GitHub (Jul 4, 2025): Setting "Use the legacy input encoding" in Poweshell settings -> Terminal emulation fixes the text problems

yindo commented

@davidanew commented on GitHub (Jul 4, 2025):

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]

@davidanew commented on GitHub (Jul 4, 2025): 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]

yindo commented

@strager commented on GitHub (Jul 4, 2025):

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

@strager commented on GitHub (Jul 4, 2025): "No text" issues might be related to num lock (see https://github.com/charmbracelet/x/issues/485). Can you try turning off num lock?

yindo commented

@strager commented on GitHub (Jul 5, 2025):

See also #143

@strager commented on GitHub (Jul 5, 2025): See also #143

yindo commented

@QDaed commented on GitHub (Jul 5, 2025):

#404 This issue still remain with the lastest patch

@QDaed commented on GitHub (Jul 5, 2025): #404 This issue still remain with the lastest patch

yindo commented

@wienans commented on GitHub (Jul 9, 2025):

@thdxr after starting the exe from the latest release i get this log (Win10).

INFO  2025-07-09T07:16:21 +63ms service=default version=0.2.13 args= opencode
INFO  2025-07-09T07:16:21 +8ms service=app cwd=C:\Users\******\opencode-windows-x64(1) creating
INFO  2025-07-09T07:16:21 +0ms service=app git
INFO  2025-07-09T07:16:21 +7ms service=bus type=storage.write subscribing
INFO  2025-07-09T07:16:21 +0ms service=app name=bus registering service
INFO  2025-07-09T07:16:21 +0ms service=format init
INFO  2025-07-09T07:16:21 +0ms service=bus type=file.edited subscribing
INFO  2025-07-09T07:16:21 +0ms service=config.hooks init
INFO  2025-07-09T07:16:21 +0ms service=bus type=file.edited subscribing
INFO  2025-07-09T07:16:21 +0ms service=bus type=session.idle subscribing
INFO  2025-07-09T07:16:21 +0ms service=app name=lsp registering service
INFO  2025-07-09T07:16:21 +0ms service=lsp initializing
INFO  2025-07-09T07:16:21 +4ms service=app name=file.watcher registering service
INFO  2025-07-09T07:16:21 +0ms service=app name=provider registering service
INFO  2025-07-09T07:16:21 +1ms service=app name=config registering service
INFO  2025-07-09T07:16:21 +4ms service=config loaded
INFO  2025-07-09T07:16:21 +2ms service=models.dev refreshing
INFO  2025-07-09T07:16:21 +0ms service=provider init
INFO  2025-07-09T07:16:21 +4ms service=app name=lsp shutdown
ERROR 2025-07-09T07:16:22 +885ms service=default name=Error message=Executable not found in $PATH: "unzip" fatal
ERROR 2025-07-09T07:16:22 +1ms service=default e=Executable not found in $PATH: "unzip" rejection

Did i miss any dependency installation process?

@wienans commented on GitHub (Jul 9, 2025): @thdxr after starting the exe from the latest release i get this log (Win10). ``` INFO 2025-07-09T07:16:21 +63ms service=default version=0.2.13 args= opencode INFO 2025-07-09T07:16:21 +8ms service=app cwd=C:\Users\******\opencode-windows-x64(1) creating INFO 2025-07-09T07:16:21 +0ms service=app git INFO 2025-07-09T07:16:21 +7ms service=bus type=storage.write subscribing INFO 2025-07-09T07:16:21 +0ms service=app name=bus registering service INFO 2025-07-09T07:16:21 +0ms service=format init INFO 2025-07-09T07:16:21 +0ms service=bus type=file.edited subscribing INFO 2025-07-09T07:16:21 +0ms service=config.hooks init INFO 2025-07-09T07:16:21 +0ms service=bus type=file.edited subscribing INFO 2025-07-09T07:16:21 +0ms service=bus type=session.idle subscribing INFO 2025-07-09T07:16:21 +0ms service=app name=lsp registering service INFO 2025-07-09T07:16:21 +0ms service=lsp initializing INFO 2025-07-09T07:16:21 +4ms service=app name=file.watcher registering service INFO 2025-07-09T07:16:21 +0ms service=app name=provider registering service INFO 2025-07-09T07:16:21 +1ms service=app name=config registering service INFO 2025-07-09T07:16:21 +4ms service=config loaded INFO 2025-07-09T07:16:21 +2ms service=models.dev refreshing INFO 2025-07-09T07:16:21 +0ms service=provider init INFO 2025-07-09T07:16:21 +4ms service=app name=lsp shutdown ERROR 2025-07-09T07:16:22 +885ms service=default name=Error message=Executable not found in $PATH: "unzip" fatal ERROR 2025-07-09T07:16:22 +1ms service=default e=Executable not found in $PATH: "unzip" rejection ``` Did i miss any dependency installation process?

yindo commented

@QDaed commented on GitHub (Jul 12, 2025):

i dont really know when will windows have a fix,it haven't usable since the first release with a lot of render bug, i love opencode as because it is good while i was using wsl2 but want to use it on windows to sync with my workflow since claude code not supported .

@QDaed commented on GitHub (Jul 12, 2025): i dont really know when will windows have a fix,it haven't usable since the first release with a lot of render bug, i love opencode as because it is good while i was using wsl2 but want to use it on windows to sync with my workflow since claude code not supported .

yindo commented

https://www.reddit.com/r/ClaudeAI/comments/1lxlezn/they_just_casually_dropped_support_for_windows/

@davidanew commented on GitHub (Jul 12, 2025):

i dont really know when will windows have a fix,it haven't usable since the first release with a lot of render bug, i love opencode as because it is good while i was using wsl2 but want to use it on windows to sync with my workflow since claude code not supported .

(Dropped means added in gen z speak apparently)

@davidanew commented on GitHub (Jul 12, 2025): > i dont really know when will windows have a fix,it haven't usable since the first release with a lot of render bug, i love opencode as because it is good while i was using wsl2 but want to use it on windows to sync with my workflow since claude code not supported . https://www.reddit.com/r/ClaudeAI/comments/1lxlezn/they_just_casually_dropped_support_for_windows/ (Dropped means added in gen z speak apparently)

yindo commented

@raymelon commented on GitHub (Jul 12, 2025):

Found this thread for Windows testers

Few problems I got
(Windows Terminal via PowerShell):

Scrolling up shows distorted views
Multi-line paste is sending each line right away instead of letting me paste it as a block of text

See attached image to see how the issues look like

@raymelon commented on GitHub (Jul 12, 2025): Found this thread for Windows testers Few problems I got (Windows Terminal via PowerShell): - Scrolling up shows distorted views - Multi-line paste is sending each line right away instead of letting me paste it as a block of text See attached image to see how the issues look like ![Image](https://github.com/user-attachments/assets/5010c9b7-62c9-467b-a6a6-3d7fe1e421e0)

yindo commented

@ArmDaniel commented on GitHub (Jul 13, 2025):

for everybody having issues with opencode on Windows, setting what @davidanew suggested related to legacy input encoding will solve the 'no text' issue. However, the scrolling will still be distorted. I solved it by opening opencode in WezTerm...so yeah, works for me that way

@ArmDaniel commented on GitHub (Jul 13, 2025): for everybody having issues with opencode on Windows, setting what @davidanew suggested related to legacy input encoding will solve the 'no text' issue. However, the scrolling will still be distorted. I solved it by opening opencode in WezTerm...so yeah, works for me that way

yindo commented

#967 feat: Replace unzip with PowerShell's built-in extraction for zip archives

@leporel commented on GitHub (Jul 14, 2025):

@leporel commented on GitHub (Jul 14, 2025): [#967 feat: Replace unzip with PowerShell's built-in extraction for zip archives](https://github.com/sst/opencode/issues/967)

yindo commented

@bramburn commented on GitHub (Jul 14, 2025):

is this because we are using go tui? or why is this happening?

@bramburn commented on GitHub (Jul 14, 2025): is this because we are using go tui? or why is this happening?

yindo commented

@CarlosGtrz commented on GitHub (Jul 14, 2025):

What Claude Code team did was to run their commands using the MSYS2 Bash shell included in Git for Windows. That may be an easier start for opencode.

@CarlosGtrz commented on GitHub (Jul 14, 2025): What Claude Code team did was to run their commands using the MSYS2 Bash shell included in Git for Windows. That may be an easier start for opencode.

yindo commented

@ikx94 commented on GitHub (Jul 15, 2025):

Looking forward to OpenCode on Windows 🙏🏻

@ikx94 commented on GitHub (Jul 15, 2025): Looking forward to OpenCode on Windows 🙏🏻

yindo commented

@bramburn commented on GitHub (Jul 15, 2025):

I'm working on a new fork for windows only. Rebuilding it with proper installation files rather than bun build.

@bramburn commented on GitHub (Jul 15, 2025): I'm working on a new fork for windows only. Rebuilding it with proper installation files rather than bun build.

yindo commented

@QDaed commented on GitHub (Jul 15, 2025):

atm i'm using bash on windows , seems it is working now

@QDaed commented on GitHub (Jul 15, 2025): atm i'm using bash on windows , seems it is working now

yindo commented

@wienans commented on GitHub (Jul 15, 2025):

@thdxr since v0.3.9 the windows.zip file is detected as virus by windows defender v0.3.8 is working fine

@wienans commented on GitHub (Jul 15, 2025): @thdxr since v0.3.9 the windows.zip file is detected as virus by windows defender v0.3.8 is working fine

yindo commented

@oenic commented on GitHub (Jul 15, 2025):

How are any of you even installing it? The site says to use the binary from the releases, but I go to the latest release and there simply isn't anything downloadable for windows

@oenic commented on GitHub (Jul 15, 2025): How are any of you even installing it? The site says to use the binary from the releases, but I go to the latest release and there simply isn't anything downloadable for windows

yindo commented

@illgitthat commented on GitHub (Jul 15, 2025):

How are any of you even installing it? The site says to use the binary from the releases, but I go to the latest release and there simply isn't anything downloadable for windows

Something happened with the latest release, but one previous has windows binary. https://github.com/sst/opencode/releases/tag/v0.3.10

@illgitthat commented on GitHub (Jul 15, 2025): > How are any of you even installing it? The site says to use the binary from the releases, but I go to the latest release and there simply isn't anything downloadable for windows Something happened with the latest release, but one previous has windows binary. https://github.com/sst/opencode/releases/tag/v0.3.10

yindo commented

@phob commented on GitHub (Jul 16, 2025):

@ -Commands aren't really working. As soon as you type anything after @ you only get no matches found.
/init isn't looking into subfolders

@phob commented on GitHub (Jul 16, 2025): @ -Commands aren't really working. As soon as you type anything after @ you only get no matches found. /init isn't looking into subfolders

yindo commented

@wienans commented on GitHub (Jul 16, 2025):

For me now the boot up of opencode on windows works. But out of what ever reason, i can not type anything in the message box. All Shortcuts work but the messagebox doesn't

@wienans commented on GitHub (Jul 16, 2025): For me now the boot up of opencode on windows works. But out of what ever reason, i can not type anything in the message box. All Shortcuts work but the messagebox doesn't

yindo commented

@leporel commented on GitHub (Jul 16, 2025):

The opencode fails to open the relative path ~

 lepa on  C:/
# opencode ~/opencode-playground
Error: Failed to change directory to C:\~\opencode-playground

this wotks -

opencode $env:USERPROFILE/opencode-playground

@leporel commented on GitHub (Jul 16, 2025): The opencode fails to open the relative path `~` ```  lepa on  C:/ # opencode ~/opencode-playground Error: Failed to change directory to C:\~\opencode-playground ``` this wotks - ``` opencode $env:USERPROFILE/opencode-playground ```

yindo commented

@TrueHOOHA commented on GitHub (Jul 17, 2025):

where is ~/.local/share/opencode/ folder located in windows? I cant find it

@TrueHOOHA commented on GitHub (Jul 17, 2025): where is ~/.local/share/opencode/ folder located in windows? I cant find it

yindo commented

@itsrainingmani commented on GitHub (Jul 18, 2025):

I've made a Chocolatey package for opencode that I'm happy to add to the chocolatey community packages. I noticed that the latest release (v0.3.19) doesn't have a windows executable at all. Is there a reason for that?

@itsrainingmani commented on GitHub (Jul 18, 2025): I've made a Chocolatey package for opencode that I'm happy to add to the chocolatey community packages. I noticed that the latest release (v0.3.19) doesn't have a windows executable at all. Is there a reason for that?

yindo commented

https://github.com/sst/opencode/pull/1189

@leporel commented on GitHub (Jul 18, 2025):

it seems call tool but not executing on windows (using ollama)

I tried making powershell.exe as a soft link to bash.exe, but it didn't help, however the model wanted to execute the command in the WSL shell and somehow it worked.

But this is not the behavior I expect, why is Bun executing commands in WSL while opencode started in powershell

{
  "id": "prt_81fbde98c001Dxxxx0iQ3orch9",
  "messageID": "msg_81fbd0ef40019381PHc5z8LvmD",
  "sessionID": "ses_7e042f5c3ffed2DGFCMg1HDSeR",
  "type": "tool",
  "tool": "bash",
  "callID": "call_qn93k91z",
  "state": {
    "status": "completed",
    "input": {
      "command": "ip -4 addr show",
      "description": "Gets IPv4 address in WSL environment"
    },
    "output": "<stdout>\n1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000\n    inet 127.0.0.1/8 scope host lo\n       valid_lft forever preferred_lft forever\n    inet 10.255.255.254/32 brd 10.255.255.254 scope global lo\n       valid_lft forever preferred_lft forever\n2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000\n    inet 172.24.110.38/20 brd 172.24.111.255 scope global eth0\n       valid_lft forever preferred_lft forever\n\n</stdout>\n<stderr>\n\n</stderr>",
    "metadata": {
      "stderr": "",
      "stdout": "1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000\n    inet 127.0.0.1/8 scope host lo\n       valid_lft forever preferred_lft forever\n    inet 10.255.255.254/32 brd 10.255.255.254 scope global lo\n       valid_lft forever preferred_lft forever\n2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000\n    inet 172.24.110.38/20 brd 172.24.111.255 scope global eth0\n       valid_lft forever preferred_lft forever\n",
      "exit": 0,
      "description": "Gets IPv4 address in WSL environment"
    },
    "title": "ip -4 addr show",
    "time": {
      "start": 1752879196557,
      "end": 1752879196632
    }
  }
}

PS: I tested this code and it works, maybe this will be implemented?

    const proc = Bun.spawn({
      cmd: process.platform === "win32" 
      ? ["powershell.exe", "-Command", params.command]
      : ["bash", "-c", params.command],

I made a PR with a fix for the bash tool call on Windows. I compiled a binary locally and am using it myself - now commands run natively in the Windows environment without relying on WSL.

@leporel commented on GitHub (Jul 18, 2025): > it seems call tool but not executing on **windows** (using ollama) I tried making powershell.exe as a soft link to bash.exe, but it didn't help, however the model wanted to execute the command in the WSL shell and somehow it worked. But this is not the behavior I expect, why is Bun executing commands in WSL while opencode started in powershell <img width="834" height="1320" alt="Image" src="https://github.com/user-attachments/assets/fb16322f-a3bd-46cf-b39d-e96056981500" /> ``` { "id": "prt_81fbde98c001Dxxxx0iQ3orch9", "messageID": "msg_81fbd0ef40019381PHc5z8LvmD", "sessionID": "ses_7e042f5c3ffed2DGFCMg1HDSeR", "type": "tool", "tool": "bash", "callID": "call_qn93k91z", "state": { "status": "completed", "input": { "command": "ip -4 addr show", "description": "Gets IPv4 address in WSL environment" }, "output": "<stdout>\n1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000\n inet 127.0.0.1/8 scope host lo\n valid_lft forever preferred_lft forever\n inet 10.255.255.254/32 brd 10.255.255.254 scope global lo\n valid_lft forever preferred_lft forever\n2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000\n inet 172.24.110.38/20 brd 172.24.111.255 scope global eth0\n valid_lft forever preferred_lft forever\n\n</stdout>\n<stderr>\n\n</stderr>", "metadata": { "stderr": "", "stdout": "1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000\n inet 127.0.0.1/8 scope host lo\n valid_lft forever preferred_lft forever\n inet 10.255.255.254/32 brd 10.255.255.254 scope global lo\n valid_lft forever preferred_lft forever\n2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000\n inet 172.24.110.38/20 brd 172.24.111.255 scope global eth0\n valid_lft forever preferred_lft forever\n", "exit": 0, "description": "Gets IPv4 address in WSL environment" }, "title": "ip -4 addr show", "time": { "start": 1752879196557, "end": 1752879196632 } } } ``` --- PS: I tested this code and it works, maybe this will be implemented? ``` const proc = Bun.spawn({ cmd: process.platform === "win32" ? ["powershell.exe", "-Command", params.command] : ["bash", "-c", params.command], ``` https://github.com/sst/opencode/pull/1189 I made a PR with a fix for the bash tool call on Windows. I compiled a binary locally and am using it myself - now commands run natively in the Windows environment without relying on WSL.

yindo commented

@Prikalel commented on GitHub (Jul 20, 2025):

C:\Windows\system32>yarn install -g opencode-ai@latest
yarn install v1.22.19
info No lockfile found.
error `--global` has been deprecated. Please run "yarn global add opencode-ai@latest" instead.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

C:\Windows\system32>yarn global add opencode-ai@latest
yarn global v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
error C:\Users\poklonsky.ale\AppData\Local\Yarn\Data\global\node_modules\opencode-ai: Command failed.
Exit code: 1
Command: node ./postinstall.mjs
Arguments:
Directory: C:\Users\poklonsky.ale\AppData\Local\Yarn\Data\global\node_modules\opencode-ai
Output:
Failed to create opencode binary symlink: Could not find package opencode-win32-x64: Cannot find module 'opencode-win32-x64/package.json'
Require stack:
- C:\Users\poklonsky.ale\AppData\Local\Yarn\Data\global\node_modules\opencode-ai\postinstall.mjs
info Visit https://yarnpkg.com/en/docs/cli/global for documentation about this command.

@Prikalel commented on GitHub (Jul 20, 2025): ``` C:\Windows\system32>yarn install -g opencode-ai@latest yarn install v1.22.19 info No lockfile found. error `--global` has been deprecated. Please run "yarn global add opencode-ai@latest" instead. info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. C:\Windows\system32>yarn global add opencode-ai@latest yarn global v1.22.19 [1/4] Resolving packages... [2/4] Fetching packages... [3/4] Linking dependencies... [4/4] Building fresh packages... error C:\Users\poklonsky.ale\AppData\Local\Yarn\Data\global\node_modules\opencode-ai: Command failed. Exit code: 1 Command: node ./postinstall.mjs Arguments: Directory: C:\Users\poklonsky.ale\AppData\Local\Yarn\Data\global\node_modules\opencode-ai Output: Failed to create opencode binary symlink: Could not find package opencode-win32-x64: Cannot find module 'opencode-win32-x64/package.json' Require stack: - C:\Users\poklonsky.ale\AppData\Local\Yarn\Data\global\node_modules\opencode-ai\postinstall.mjs info Visit https://yarnpkg.com/en/docs/cli/global for documentation about this command. ```

yindo commented

@itsrainingmani commented on GitHub (Jul 20, 2025):

The chocolatey package for opencode has passed automated validation and I'm waiting on moderator approval to have it be officially listed (and to release updated versions). But in the meantime, v0.3.43 is available for download - https://community.chocolatey.org/packages/opencode/0.3.43

@itsrainingmani commented on GitHub (Jul 20, 2025): The chocolatey package for opencode has passed automated validation and I'm waiting on moderator approval to have it be officially listed (and to release updated versions). But in the meantime, `v0.3.43` is available for download - https://community.chocolatey.org/packages/opencode/0.3.43

yindo commented

@RedWilly commented on GitHub (Jul 21, 2025):

The chocolatey package for opencode has passed automated validation and I'm waiting on moderator approval to have it be officially listed (and to release updated versions). But in the meantime, v0.3.43 is available for download - https://community.chocolatey.org/packages/opencode/0.3.43

yeah nice was able to install using chocolate. thanks

@RedWilly commented on GitHub (Jul 21, 2025): > The chocolatey package for opencode has passed automated validation and I'm waiting on moderator approval to have it be officially listed (and to release updated versions). But in the meantime, `v0.3.43` is available for download - https://community.chocolatey.org/packages/opencode/0.3.43 yeah nice was able to install using chocolate. thanks

yindo commented

@Slach commented on GitHub (Jul 21, 2025):

scoop windows installation also wait PR rewview
https://github.com/ScoopInstaller/Extras/pull/15843

@Slach commented on GitHub (Jul 21, 2025): scoop windows installation also wait PR rewview https://github.com/ScoopInstaller/Extras/pull/15843

yindo commented

@bramburn commented on GitHub (Jul 21, 2025):

feel like killing myself with all these issues.

On Mon, 21 Jul 2025 at 15:39, Eugene Klimov @.***>
wrote:

Slach left a comment (sst/opencode#631)
https://github.com/sst/opencode/issues/631#issuecomment-3097060055

scoop windows installation also wait PR rewview
ScoopInstaller/Extras#15843
https://github.com/ScoopInstaller/Extras/pull/15843

—
Reply to this email directly, view it on GitHub
https://github.com/sst/opencode/issues/631#issuecomment-3097060055, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUTT3MKCOHQKAH4MHXH75L3JT3Q5AVCNFSM6AAAAACAVSP5UGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAOJXGA3DAMBVGU
.
You are receiving this because you commented.Message ID:
@.***>

@bramburn commented on GitHub (Jul 21, 2025): feel like killing myself with all these issues. On Mon, 21 Jul 2025 at 15:39, Eugene Klimov ***@***.***> wrote: > *Slach* left a comment (sst/opencode#631) > <https://github.com/sst/opencode/issues/631#issuecomment-3097060055> > > scoop windows installation also wait PR rewview > ScoopInstaller/Extras#15843 > <https://github.com/ScoopInstaller/Extras/pull/15843> > > — > Reply to this email directly, view it on GitHub > <https://github.com/sst/opencode/issues/631#issuecomment-3097060055>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACUTT3MKCOHQKAH4MHXH75L3JT3Q5AVCNFSM6AAAAACAVSP5UGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAOJXGA3DAMBVGU> > . > You are receiving this because you commented.Message ID: > ***@***.***> >

yindo commented

@yokowasis commented on GitHub (Jul 25, 2025):

half page scroll down is broken on powershell and cmd on windows terminal. it works fine on alacritty. bash also works fine. wsl also works fine.

@yokowasis commented on GitHub (Jul 25, 2025): half page scroll down is broken on powershell and cmd on windows terminal. it works fine on alacritty. bash also works fine. wsl also works fine.

yindo commented

@sanathusk commented on GitHub (Jul 28, 2025):

Please add support for Windows 11 arm version

@sanathusk commented on GitHub (Jul 28, 2025): Please add support for Windows 11 arm version

yindo commented

@Orcomp commented on GitHub (Jul 29, 2025):

Installed opencode with scoop and am running it in bash. Mouse wheel works (which is a good start).

Update: It's not working today. Not sure what changed.

@Orcomp commented on GitHub (Jul 29, 2025): Installed opencode with scoop and am running it in bash. Mouse wheel works (which is a good start). Update: It's not working today. Not sure what changed.

yindo commented

@Badbird5907 commented on GitHub (Jul 29, 2025):

Please add support for Windows 11 arm version

Opencode works fine for me under emulation

@Badbird5907 commented on GitHub (Jul 29, 2025): > Please add support for Windows 11 arm version Opencode works fine for me under emulation

yindo commented

@arpan-astreyan commented on GitHub (Aug 7, 2025):

Still not working!!
Not able to use this great cli.

@arpan-astreyan commented on GitHub (Aug 7, 2025): Still not working!! Not able to use this great cli.

yindo commented

@chjudge commented on GitHub (Aug 7, 2025):

The two issues I've seen when trying to install with bun have been the package name not matching what the postinstall script looks for and the opencode.bunx file that bun generates alongside the executable being malformed (it tries to run with /bin/sh instead of cmd) I have a pull request open for the first issue and have made a sort of shim that will generate the correct .bunx file for now but looking to dig into that at some point, hoping it is maybe a tweak in the build process

@chjudge commented on GitHub (Aug 7, 2025): The two issues I've seen when trying to install with bun have been the package name not matching what the postinstall script looks for and the opencode.bunx file that bun generates alongside the executable being malformed (it tries to run with /bin/sh instead of cmd) I have a pull request open for the first issue and have made a sort of shim that will generate the correct .bunx file for now but looking to dig into that at some point, hoping it is maybe a tweak in the build process

yindo commented

@ledmaster commented on GitHub (Aug 8, 2025):

Tested version 0.4.1 today on Windows 11 with Powershell. Mostly fine, just scrolling down during a session messes up the messages. Scrolling up doesn't have issues. Otherwise no issues.

@ledmaster commented on GitHub (Aug 8, 2025): Tested version 0.4.1 today on Windows 11 with Powershell. Mostly fine, just **scrolling down** during a session messes up the messages. Scrolling up doesn't have issues. Otherwise no issues.

yindo commented

@INGCapaDev commented on GitHub (Aug 8, 2025):

Please fix the scrolling down +1

@INGCapaDev commented on GitHub (Aug 8, 2025): Please fix the scrolling down +1

yindo commented

@ledmaster commented on GitHub (Aug 9, 2025):

Scrolling down and up with mouse and PgUp,PgDown working fine in Windows 11, Powershell 7 inside Alacritty with Opencode 0.4.2

Got some "virus detected" messages yesterday when downloading this version, but none today

@ledmaster commented on GitHub (Aug 9, 2025): Scrolling down and up with mouse and PgUp,PgDown working fine in Windows 11, Powershell 7 inside Alacritty with Opencode 0.4.2 Got some "virus detected" messages yesterday when downloading this version, but none today

yindo commented

@nbiotminsk commented on GitHub (Aug 17, 2025):

How to change settings API

@nbiotminsk commented on GitHub (Aug 17, 2025): How to change settings API

yindo commented

@tylertylerday commented on GitHub (Aug 18, 2025):

Just installed using "choco install opencode" and everything is working! Great work! Windows 11 / Windows terminal

@tylertylerday commented on GitHub (Aug 18, 2025): Just installed using "choco install opencode" and everything is working! Great work! Windows 11 / Windows terminal

yindo commented

@ledmaster commented on GitHub (Aug 19, 2025):

Just installed using "choco install opencode" and everything is working! Great work! Windows 11 / Windows terminal

Are models able to find stuff using Grep for you?

@ledmaster commented on GitHub (Aug 19, 2025): > Just installed using "choco install opencode" and everything is working! Great work! Windows 11 / Windows terminal Are models able to find stuff using Grep for you?

yindo commented

@rekram1-node commented on GitHub (Aug 19, 2025):

Have any of yall had problems specifically trying to use opencode with an npm install instead of choco? I heard someone in discord say that npm install didn't work but choco does

@rekram1-node commented on GitHub (Aug 19, 2025): Have any of yall had problems specifically trying to use opencode with an npm install instead of choco? I heard someone in discord say that npm install didn't work but choco does

yindo commented

@wienans commented on GitHub (Aug 20, 2025):

Have any of yall had problems specifically trying to use opencode with an npm install instead of choco? I heard someone in discord say that npm install didn't work but choco does

I actually used straight up binary. Is there a difference in install methods🤔

@wienans commented on GitHub (Aug 20, 2025): > Have any of yall had problems specifically trying to use opencode with an npm install instead of choco? I heard someone in discord say that npm install didn't work but choco does I actually used straight up binary. Is there a difference in install methods🤔

yindo commented

@krymancer commented on GitHub (Aug 21, 2025):

Since the repo don't have an discusstions tab, I ask here:

It's planned to have an winget package?

@krymancer commented on GitHub (Aug 21, 2025): Since the repo don't have an discusstions tab, I ask here: It's planned to have an winget package?

yindo commented

@kytpbs commented on GitHub (Aug 24, 2025):

NPM failed miserably, but I was able to install it through Winget, which worked nearly perfectly. I'm not sure by whom or how, but it's available in Winget.

In the /help view, when I scroll down, only the value at the very bottom changes, while the rest remain the same until I scroll back up. Then it works correctly. If I scroll to the bottom and keep rapidly pressing up and down, all of the help menus get filled with input_submit.

@kytpbs commented on GitHub (Aug 24, 2025): NPM failed miserably, but I was able to install it through Winget, which worked nearly perfectly. I'm not sure by whom or how, but it's available in Winget. In the `/help` view, when I scroll down, only the value at the very bottom changes, while the rest remain the same until I scroll back up. Then it works correctly. If I scroll to the bottom and keep rapidly pressing up and down, all of the help menus get filled with `input_submit`.

yindo commented

@robertmclaws commented on GitHub (Aug 26, 2025):

I got this working on WinGet and it's working against Grok Free. Please fix scrolling though, this is a HUGE issue for me, especially because Grok is chatty AF.

@robertmclaws commented on GitHub (Aug 26, 2025): I got this working on WinGet and it's working against Grok Free. Please fix scrolling though, this is a HUGE issue for me, especially because Grok is chatty AF.

yindo commented

@crazy-treyn commented on GitHub (Aug 26, 2025):

I got this working on WinGet and it's working against Grok Free. Please fix scrolling though, this is a HUGE issue for me, especially because Grok is chatty AF.

Came here to say this. Scrolling bug makes it virtually unusable on Windows (non WSL).

Otherwise seems to be working. I was able to install via winget too.

@crazy-treyn commented on GitHub (Aug 26, 2025): > I got this working on WinGet and it's working against Grok Free. Please fix scrolling though, this is a HUGE issue for me, especially because Grok is chatty AF. Came here to say this. Scrolling bug makes it virtually unusable on Windows (non WSL). Otherwise seems to be working. I was able to install via winget too.

yindo commented

@robertmclaws commented on GitHub (Aug 26, 2025):

I discovered that if you resize the window you can at least read what's there because it triggers a re-render.

@robertmclaws commented on GitHub (Aug 26, 2025): I discovered that if you resize the window you can at least read what's there because it triggers a re-render.

yindo commented

@leporel commented on GitHub (Aug 27, 2025):

I discovered that if you resize the window you can at least read what's there because it triggers a re-render.

PgUp / PgDn also make it readable

@leporel commented on GitHub (Aug 27, 2025): > I discovered that if you resize the window you can at least read what's there because it triggers a re-render. PgUp / PgDn also make it readable

yindo commented

@dylbarne commented on GitHub (Aug 27, 2025):

documented method of Windows install with bun install -g opencode-ai seems to be working alright for me
(npm is my preferred package manager, but was getting various installation issues on Windows)

not sure if is expected, but to note: the opencode.exe in my %USERPROFILE%\.bun\.bin did not work, had to add to PATH and use the one instead from %USERPROFILE%\.bun\install\global\node_modules\opencode-windows-x64\bin

@dylbarne commented on GitHub (Aug 27, 2025): [documented](https://opencode.ai/) method of Windows install with `bun install -g opencode-ai` seems to be working alright for me _(npm is my preferred package manager, but was getting various installation issues on Windows)_ not sure if is expected, but to note: the opencode.exe in my %USERPROFILE%\\.bun\\.bin did **_not_** work, had to add to PATH and use the one instead from %USERPROFILE%\\.bun\install\global\node_modules\opencode-windows-x64\bin

yindo commented

@thomaseleff commented on GitHub (Aug 29, 2025):

@robertmclaws

I got this working on WinGet and it's working against Grok Free. Please fix scrolling though, this is a HUGE issue for me, especially because Grok is chatty AF.

Certainly not a perfect solution, but I just ask the llm to create markdown files containing its responses in a particular folder in the repo and omit that folder in .gitignore.

The drawback (aside from the obvious UX drawback) is you can't really use the plan mode since the llm does not have write permission in that mode.

@thomaseleff commented on GitHub (Aug 29, 2025): @robertmclaws > I got this working on WinGet and it's working against Grok Free. Please fix scrolling though, this is a HUGE issue for me, especially because Grok is chatty AF. Certainly not a perfect solution, but I just ask the llm to create markdown files containing its responses in a particular folder in the repo and omit that folder in .gitignore. The drawback (aside from the obvious UX drawback) is you can't really use the plan mode since the llm does not have write permission in that mode.

yindo commented

@notkiran commented on GitHub (Sep 8, 2025):

bun install -g opencode-ai

installs the opencode properly, but when, opncode is run I get this error

`PS C:\Users\Administrator> opencode
error: interpreter executable "/bin/sh" not found in %PATH%

Bun failed to remap this bin to its proper location within node_modules.
This is an indication of a corrupted node_modules directory.

Please run 'bun install --force' in the project root and try
it again. If this message persists, please open an issue:
https://github.com/oven-sh/bun/issues`

@notkiran commented on GitHub (Sep 8, 2025): bun install -g opencode-ai installs the opencode properly, but when, opncode is run I get this error `PS C:\Users\Administrator> opencode error: interpreter executable "/bin/sh" not found in %PATH% Bun failed to remap this bin to its proper location within node_modules. This is an indication of a corrupted node_modules directory. Please run 'bun install --force' in the project root and try it again. If this message persists, please open an issue: [https://github.com/oven-sh/bun/issues`](https://github.com/oven-sh/bun/issues%60)

yindo commented

@NSPC911 commented on GitHub (Sep 8, 2025):

I got this working on WinGet and it's working against Grok Free. Please fix scrolling though, this is a HUGE issue for me, especially because Grok is chatty AF.

Came here to say this. Scrolling bug makes it virtually unusable on Windows (non WSL).

super inconsistent based on my testing. using opencode via scoop
I had issues with scrolling, so I decided to force reinstallation, it works now, not sure why it is so, but thought I'd share
before reinstallation, I got this error message every time I quit

panic: close of closed channel

goroutine 1 [running]:
github.com/sst/opencode/internal/components/status.(*statusComponent).Cleanup(0xc00007a360)
        /home/runner/work/opencode/opencode/packages/tui/internal/components/status/status.go:319 +0x25
github.com/sst/opencode/internal/tui.Model.Cleanup(...)
        /home/runner/work/opencode/opencode/packages/tui/internal/tui/tui.go:914
main.main()
        /home/runner/work/opencode/opencode/packages/tui/cmd/opencode/main.go:166 +0xce9

and also bun install -g opencode-ai yields the same message as the above comment, it cannot find /bin/sh on PATH

@NSPC911 commented on GitHub (Sep 8, 2025): > > I got this working on WinGet and it's working against Grok Free. Please fix scrolling though, this is a HUGE issue for me, especially because Grok is chatty AF. > > Came here to say this. Scrolling bug makes it virtually unusable on Windows (non WSL). super inconsistent based on my testing. using opencode via scoop I had issues with scrolling, so I decided to force reinstallation, it works now, not sure why it is so, but thought I'd share before reinstallation, I got this error message every time I quit ``` panic: close of closed channel goroutine 1 [running]: github.com/sst/opencode/internal/components/status.(*statusComponent).Cleanup(0xc00007a360) /home/runner/work/opencode/opencode/packages/tui/internal/components/status/status.go:319 +0x25 github.com/sst/opencode/internal/tui.Model.Cleanup(...) /home/runner/work/opencode/opencode/packages/tui/internal/tui/tui.go:914 main.main() /home/runner/work/opencode/opencode/packages/tui/cmd/opencode/main.go:166 +0xce9 ``` and also `bun install -g opencode-ai` yields the same message as the above comment, it cannot find `/bin/sh` on `PATH`

yindo commented

@notkiran commented on GitHub (Sep 9, 2025):

how to fix the scrolling issue? can anyone or @NSPC911 let me know for windows, which way to install

@notkiran commented on GitHub (Sep 9, 2025): how to fix the scrolling issue? can anyone or @NSPC911 let me know for windows, which way to install

yindo commented

@NSPC911 commented on GitHub (Sep 9, 2025):

how to fix the scrolling issue? can anyone or @NSPC911 let me know for windows, which way to install

I'm currently using scoop, so it is as simple as

scoop bucket add extras
scoop install extras/opencode

@NSPC911 commented on GitHub (Sep 9, 2025): > how to fix the scrolling issue? can anyone or [@NSPC911](https://github.com/NSPC911) let me know for windows, which way to install I'm currently using [scoop](https://scoop.sh), so it is as simple as ```pwsh scoop bucket add extras scoop install extras/opencode ```

yindo commented

@notkiran commented on GitHub (Sep 9, 2025):

the scroll issue is still there on scoop install also

@notkiran commented on GitHub (Sep 9, 2025): the scroll issue is still there on scoop install also

yindo commented

https://github.com/user-attachments/assets/a2b930b9-b2a6-499c-890f-a5690ca056c8

@NSPC911 commented on GitHub (Sep 9, 2025):

I also noticed an issue, opencode released their latest update about a few hours ago, and I was using opencode at that time. It was working perfectly fine, until it 'updated' to the latest version itself, without scoop doing anything. That's when it straight up stopped scrolling. Take this as a pinch of salt, I just want to contribute what I observed, but I'd like to see people test it out by reinstalling opencode if the scroll isn't working.

@NSPC911 commented on GitHub (Sep 9, 2025): https://github.com/user-attachments/assets/a2b930b9-b2a6-499c-890f-a5690ca056c8 I also noticed an issue, opencode released their latest update about a few hours ago, and I was using opencode at that time. It was working perfectly fine, until it 'updated' to the latest version itself, without scoop doing anything. That's when it straight up stopped scrolling. Take this as a pinch of salt, I just want to contribute what I observed, but I'd like to see people test it out by reinstalling opencode if the scroll isn't working.

yindo commented

https://github.com/user-attachments/assets/3814d444-dee3-44c0-a969-061c23c11b51

@NSPC911 commented on GitHub (Sep 9, 2025):

I also want to check whether people have this issue, where you cannot attach files via opencode?

@NSPC911 commented on GitHub (Sep 9, 2025): I also want to check whether people have this issue, where you cannot attach files via opencode? https://github.com/user-attachments/assets/3814d444-dee3-44c0-a969-061c23c11b51

yindo commented

@itsrainingmani commented on GitHub (Sep 9, 2025):

bun install -g opencode-ai

installs the opencode properly, but when, opncode is run I get this error

`PS C:\Users\Administrator> opencode error: interpreter executable "/bin/sh" not found in %PATH%

Bun failed to remap this bin to its proper location within node_modules. This is an indication of a corrupted node_modules directory.

Please run 'bun install --force' in the project root and try it again. If this message persists, please open an issue: https://github.com/oven-sh/bun/issues`

we put out a patch for this, but there is still some nagging issue around how the shims are being auto-generated on Windows. I'm working on fixing this!

@itsrainingmani commented on GitHub (Sep 9, 2025): > bun install -g opencode-ai > > installs the opencode properly, but when, opncode is run I get this error > > `PS C:\Users\Administrator> opencode error: interpreter executable "/bin/sh" not found in %PATH% > > Bun failed to remap this bin to its proper location within node_modules. This is an indication of a corrupted node_modules directory. > > Please run 'bun install --force' in the project root and try it again. If this message persists, please open an issue: [https://github.com/oven-sh/bun/issues`](https://github.com/oven-sh/bun/issues%60) we put out a patch for this, but there is still some nagging issue around how the shims are being auto-generated on Windows. I'm working on fixing this!

yindo commented

@itsrainingmani commented on GitHub (Sep 9, 2025):

I also want to check whether people have this issue, where you cannot attach files via opencode?
2025-09-09.22-12-51.mp4

Yes I also have the same issue and am trying to fix this as well 😅

@itsrainingmani commented on GitHub (Sep 9, 2025): > I also want to check whether people have this issue, where you cannot attach files via opencode? > 2025-09-09.22-12-51.mp4 Yes I also have the same issue and am trying to fix this as well 😅

yindo commented

@ykiran commented on GitHub (Sep 10, 2025):

I'm trying to add GLM 4.5, but unable to paste the API key when asked to. Anyone else facing this issue?

Windows 10 Pro (19045.6216)

Using latest: 0.6.10

WezTerm: 20240203-110809-5046fc22

@ykiran commented on GitHub (Sep 10, 2025): I'm trying to add GLM 4.5, but unable to paste the API key when asked to. Anyone else facing this issue? <img width="337" height="220" alt="Image" src="https://github.com/user-attachments/assets/c16f4629-e362-43c3-a431-3d8730118fac" /> Windows 10 Pro (19045.6216) Using latest: 0.6.10 WezTerm: 20240203-110809-5046fc22

yindo commented

@NSPC911 commented on GitHub (Sep 10, 2025):

I'm trying to add GLM 4.5, but unable to paste the API key when asked to. Anyone else facing this issue?

I had that issue as well. What I used was to 'literal' pasting to paste the API key

Wezterm's pasting is a bit funky at times, so normal ctrl + v may not work, so I use ctrl + shift + v to paste text as if I typed it out.

@NSPC911 commented on GitHub (Sep 10, 2025): > I'm trying to add GLM 4.5, but unable to paste the API key when asked to. Anyone else facing this issue? I had that issue as well. What I used was to 'literal' pasting to paste the API key Wezterm's pasting is a bit funky at times, so normal <kbd>ctrl + v</kbd> may not work, so I use <kbd>ctrl + shift + v</kbd> to paste text as if I typed it out.

yindo commented

@ykiran commented on GitHub (Sep 10, 2025):

I'm trying to add GLM 4.5, but unable to paste the API key when asked to. Anyone else facing this issue?

I had that issue as well. What I used was to 'literal' pasting to paste the API key

Wezterm's pasting is a bit funky at times, so normal ctrl + v may not work, so I use ctrl + shift + v to paste text as if I typed it out.

This worked, thanks a lot @NSPC911

@ykiran commented on GitHub (Sep 10, 2025): > > I'm trying to add GLM 4.5, but unable to paste the API key when asked to. Anyone else facing this issue? > > I had that issue as well. What I used was to 'literal' pasting to paste the API key > > Wezterm's pasting is a bit funky at times, so normal ctrl + v may not work, so I use ctrl + shift + v to paste text as if I typed it out. This worked, thanks a lot @NSPC911

yindo commented

@notkiran commented on GitHub (Sep 10, 2025):

how to fix the scrolling issue? can anyone or @NSPC911 let me know for windows, which way to install

I'm currently using scoop, so it is as simple as

scoop bucket add extras
scoop install extras/opencode

In this scoop install method, the scroll bug is not there, it displays content properly, but there is no scroll functionality, so whatever content out of display window cannot be accessed again or scrolled @NSPC911

@notkiran commented on GitHub (Sep 10, 2025): > > how to fix the scrolling issue? can anyone or [@NSPC911](https://github.com/NSPC911) let me know for windows, which way to install > > I'm currently using [scoop](https://scoop.sh), so it is as simple as > > scoop bucket add extras > scoop install extras/opencode In this scoop install method, the scroll bug is not there, it displays content properly, but there is no scroll functionality, so whatever content out of display window cannot be accessed again or scrolled @NSPC911

yindo commented

@NSPC911 commented on GitHub (Sep 10, 2025):

how to fix the scrolling issue? can anyone or @NSPC911 let me know for windows, which way to install

I'm currently using scoop, so it is as simple as
scoop bucket add extras
scoop install extras/opencode

In this scoop install method, the scroll bug is not there, it displays content properly, but there is no scroll functionality, so whatever content out of display window cannot be accessed again or scrolled @NSPC911

what terminal are you using? i don't think it should matter, because it works on Wezterm (currently using), Rio, Alacritty and Windows Terminal (Preview)

@NSPC911 commented on GitHub (Sep 10, 2025): > > > how to fix the scrolling issue? can anyone or [@NSPC911](https://github.com/NSPC911) let me know for windows, which way to install > > > > > > I'm currently using [scoop](https://scoop.sh), so it is as simple as > > scoop bucket add extras > > scoop install extras/opencode > > In this scoop install method, the scroll bug is not there, it displays content properly, but there is no scroll functionality, so whatever content out of display window cannot be accessed again or scrolled [@NSPC911](https://github.com/NSPC911) what terminal are you using? i don't think it should matter, because it works on Wezterm (currently using), Rio, Alacritty and Windows Terminal (Preview)

yindo commented

@notkiran commented on GitHub (Sep 10, 2025):

how to fix the scrolling issue? can anyone or @NSPC911 let me know for windows, which way to install

I'm currently using scoop, so it is as simple as
scoop bucket add extras
scoop install extras/opencode

In this scoop install method, the scroll bug is not there, it displays content properly, but there is no scroll functionality, so whatever content out of display window cannot be accessed again or scrolled @NSPC911

what terminal are you using? i don't think it should matter, because it works on Wezterm (currently using), Rio, Alacritty and Windows Terminal (Preview)

in v0.7.0 scroll is buggy in new windows terminal, old PowerShell , new PowerShell and also in PowerShell preview

scroll is only working proper in scoop install and wezterm

@notkiran commented on GitHub (Sep 10, 2025): > > > > how to fix the scrolling issue? can anyone or [@NSPC911](https://github.com/NSPC911) let me know for windows, which way to install > > > > > > > > > I'm currently using [scoop](https://scoop.sh), so it is as simple as > > > scoop bucket add extras > > > scoop install extras/opencode > > > > > > In this scoop install method, the scroll bug is not there, it displays content properly, but there is no scroll functionality, so whatever content out of display window cannot be accessed again or scrolled [@NSPC911](https://github.com/NSPC911) > > what terminal are you using? i don't think it should matter, because it works on Wezterm (currently using), Rio, Alacritty and Windows Terminal (Preview) in v0.7.0 scroll is buggy in new windows terminal, old PowerShell , new PowerShell and also in PowerShell preview scroll is only working proper in scoop install and wezterm

yindo commented

@AmeowCAT commented on GitHub (Sep 11, 2025):

how to fix the scrolling issue? can anyone or @NSPC911 let me know for windows, which way to install

I'm currently using scoop, so it is as simple as
scoop bucket add extras
scoop install extras/opencode

In this scoop install method, the scroll bug is not there, it displays content properly, but there is no scroll functionality, so whatever content out of display window cannot be accessed again or scrolled @NSPC911

what terminal are you using? i don't think it should matter, because it works on Wezterm (currently using), Rio, Alacritty and Windows Terminal (Preview)

in v0.7.0 scroll is buggy in new windows terminal, old PowerShell , new PowerShell and also in PowerShell preview

scroll is only working proper in scoop install and wezterm

This solved my scrolling issue in Windows Terminal (Preview)
setx TERM xterm-256color

@AmeowCAT commented on GitHub (Sep 11, 2025): > > > > > how to fix the scrolling issue? can anyone or [@NSPC911](https://github.com/NSPC911) let me know for windows, which way to install > > > > > > > > > > > > I'm currently using [scoop](https://scoop.sh), so it is as simple as > > > > scoop bucket add extras > > > > scoop install extras/opencode > > > > > > > > > In this scoop install method, the scroll bug is not there, it displays content properly, but there is no scroll functionality, so whatever content out of display window cannot be accessed again or scrolled [@NSPC911](https://github.com/NSPC911) > > > > > > what terminal are you using? i don't think it should matter, because it works on Wezterm (currently using), Rio, Alacritty and Windows Terminal (Preview) > > in v0.7.0 scroll is buggy in new windows terminal, old PowerShell , new PowerShell and also in PowerShell preview > > scroll is only working proper in scoop install and wezterm This solved my scrolling issue in Windows Terminal (Preview) `setx TERM xterm-256color`

yindo commented

@Slach commented on GitHub (Sep 11, 2025):

@AmeowCAT thaks for sharing workaround

@Slach commented on GitHub (Sep 11, 2025): @AmeowCAT thaks for sharing workaround

yindo commented

@NSPC911 commented on GitHub (Sep 11, 2025):

other replies

how to fix the scrolling issue? can anyone or @NSPC911 let me know for windows, which way to install

I'm currently using scoop, so it is as simple as
scoop bucket add extras
scoop install extras/opencode

In this scoop install method, the scroll bug is not there, it displays content properly, but there is no scroll functionality, so whatever content out of display window cannot be accessed again or scrolled @NSPC911

what terminal are you using? i don't think it should matter, because it works on Wezterm (currently using), Rio, Alacritty and Windows Terminal (Preview)

in v0.7.0 scroll is buggy in new windows terminal, old PowerShell , new PowerShell and also in PowerShell preview
scroll is only working proper in scoop install and wezterm

This solved my scrolling issue in Windows Terminal (Preview) setx TERM xterm-256color

wouldn't that ruin other terminals, that may or may not support xterm-256color? surely some terminals support the truecolor or just cannot support xterm-256color palette

@NSPC911 commented on GitHub (Sep 11, 2025): <details> <summary>other replies</summary> <p> > > > > > > how to fix the scrolling issue? can anyone or [@NSPC911](https://github.com/NSPC911) let me know for windows, which way to install > > > > > > > > > > > > > > > I'm currently using [scoop](https://scoop.sh), so it is as simple as > > > > > scoop bucket add extras > > > > > scoop install extras/opencode > > > > > > > > > > > > In this scoop install method, the scroll bug is not there, it displays content properly, but there is no scroll functionality, so whatever content out of display window cannot be accessed again or scrolled [@NSPC911](https://github.com/NSPC911) > > > > > > > > > what terminal are you using? i don't think it should matter, because it works on Wezterm (currently using), Rio, Alacritty and Windows Terminal (Preview) > > > > <p> </details> > > in v0.7.0 scroll is buggy in new windows terminal, old PowerShell , new PowerShell and also in PowerShell preview > > scroll is only working proper in scoop install and wezterm > > This solved my scrolling issue in Windows Terminal (Preview) `setx TERM xterm-256color` wouldn't that ruin other terminals, that may or may not support `xterm-256color`? surely some terminals support the `truecolor` or just cannot support `xterm-256color` palette

yindo commented

@AmeowCAT commented on GitHub (Sep 11, 2025):

other replies

in v0.7.0 scroll is buggy in new windows terminal, old PowerShell , new PowerShell and also in PowerShell preview
scroll is only working proper in scoop install and wezterm

This solved my scrolling issue in Windows Terminal (Preview) setx TERM xterm-256color

wouldn't that ruin other terminals, that may or may not support xterm-256color? surely some terminals support the truecolor or just cannot support xterm-256color palette

yes, this isn’t a universal solution, but it may help point the way.

@AmeowCAT commented on GitHub (Sep 11, 2025): > other replies > > > in v0.7.0 scroll is buggy in new windows terminal, old PowerShell , new PowerShell and also in PowerShell preview > > > scroll is only working proper in scoop install and wezterm > > > > > > This solved my scrolling issue in Windows Terminal (Preview) `setx TERM xterm-256color` > > wouldn't that ruin other terminals, that may or may not support `xterm-256color`? surely some terminals support the `truecolor` or just cannot support `xterm-256color` palette yes, this isn’t a universal solution, but it may help point the way.

yindo commented

@nikitakot commented on GitHub (Sep 15, 2025):

can i ask what's the status of this issue? how reliably opencode can be used now natively on Windows compared to Linux/Mac?

@nikitakot commented on GitHub (Sep 15, 2025): can i ask what's the status of this issue? how reliably opencode can be used now natively on Windows compared to Linux/Mac?

yindo commented

@rekram1-node commented on GitHub (Sep 15, 2025):

I still think there is a bit more work to do to have best experience

@rekram1-node commented on GitHub (Sep 15, 2025): I still think there is a bit more work to do to have best experience

yindo commented

@nielpattin commented on GitHub (Sep 23, 2025):

~~No one mention pasting image yet?~~
~~Pasting copied image, not doing anything btw~~
~~Hope to have a fix in place soon!~~

I think it working for paste image and scroll issue somehow on alacritty
https://github.com/sst/opencode/issues/2821#issuecomment-3369798611

@nielpattin commented on GitHub (Sep 23, 2025): ~~No one mention pasting image yet?~~ ~~Pasting copied image, not doing anything btw~~ ~~Hope to have a fix in place soon!~~ I think it working for paste image and scroll issue somehow on [alacritty](https://github.com/alacritty/alacritty) https://github.com/sst/opencode/issues/2821#issuecomment-3369798611

yindo commented

@JosXa commented on GitHub (Oct 12, 2025):

Adding my voice here to agree and report that scrolling down is completely borked in Windows Terminal, but works in Alacritty (which I installed just to be able to use opencode).

Is anyone able to add new lines via input_newline (shift+enter by default) in Alacritty? This works in Windows Terminal, but in Alacritty it just sends the message. I guess the shift key is intercepted somehow, because rebinding it to ctrl+enter works.

@JosXa commented on GitHub (Oct 12, 2025): Adding my voice here to agree and report that scrolling down is completely borked in Windows Terminal, but works in Alacritty (which I installed just to be able to use opencode). Is anyone able to add new lines via `input_newline` (<kbd>shift+enter</kbd> by default) in Alacritty? This works in Windows Terminal, but in Alacritty it just sends the message. I guess the shift key is intercepted somehow, because rebinding it to <kbd>ctrl+enter</kbd> works.

yindo commented

@BurgessTG commented on GitHub (Oct 12, 2025):

Taking a hack at making windows solid =]

@BurgessTG commented on GitHub (Oct 12, 2025): Taking a hack at making windows solid =]

yindo commented

@BurgessTG commented on GitHub (Oct 13, 2025):

I have a fix for the binary installation using a js wrapper on windows, also LSP pathing and tooling that seems to work okay in Dev

@BurgessTG commented on GitHub (Oct 13, 2025): I have a fix for the binary installation using a js wrapper on windows, also LSP pathing and tooling that seems to work okay in Dev

yindo commented

@Derjyn commented on GitHub (Oct 14, 2025):

Another issue I didn't see mentioned here, is non-Windows commands are constantly being run. Rather than dir, ls is run. cmd.exe or similar should also be utilized. Basically a simple review of the tools you guys have for MacOS and Linux need to be translated to Windows (even though apparently no one uses Windows nowadays?).

This poor Windows bit is the only negative I can personally spot with OpenCode. Had no issues on several other similar platforms I audited and put through testing. Charm, Claude Code, etc... These little bugger issues seem like easy wins to gain a bigger portion of this domain, and would certainly make your users happy!

@Derjyn commented on GitHub (Oct 14, 2025): Another issue I didn't see mentioned here, is non-Windows commands are constantly being run. Rather than `dir`, `ls` is run. `cmd.exe` or similar should also be utilized. Basically a simple review of the tools you guys have for MacOS and Linux need to be translated to Windows (even though apparently no one uses Windows nowadays?). This poor Windows bit is the only negative I can personally spot with OpenCode. Had no issues on several other similar platforms I audited and put through testing. Charm, Claude Code, etc... These little bugger issues seem like easy wins to gain a bigger portion of this domain, and would certainly make your users happy!

yindo commented

@NSPC911 commented on GitHub (Oct 14, 2025):

^ yeah, it fails to open files, list or just do things in general because commands used are posix commands that do not work on windows.
either powershell is used, or cmd should be used. git bash or wsl is fine, but it shouldnt be a requirement to run opencode

@NSPC911 commented on GitHub (Oct 14, 2025): ^ yeah, it fails to open files, list or just do things in general because commands used are posix commands that do not work on windows. either powershell is used, or cmd should be used. git bash or wsl is fine, but it shouldnt be a requirement to run opencode

yindo commented

@rekram1-node commented on GitHub (Oct 14, 2025):

thanks for the feedback guys, I hope we can get it to a better state for you all soon

@rekram1-node commented on GitHub (Oct 14, 2025): thanks for the feedback guys, I hope we can get it to a better state for you all soon

yindo commented

@nielpattin commented on GitHub (Oct 14, 2025):

^ yeah, it fails to open files, list or just do things in general because commands used are posix commands that do not work on windows. either powershell is used, or cmd should be used. git bash or wsl is fine, but it shouldnt be a requirement to run opencode

I would like to support nushell as default for windows because it is kinda like POSIX shell bash, zsh. I very tired of telling llm to run cmd every time it's trying to run bash command on cmd shell. IDK but when use on Windows (not in wsl) it only run cmd command. No offense but powershell and cmd syntax gonna take me miles before even understand what it actually does.

@nielpattin commented on GitHub (Oct 14, 2025): > ^ yeah, it fails to open files, list or just do things in general because commands used are posix commands that do not work on windows. either powershell is used, or cmd should be used. git bash or wsl is fine, but it shouldnt be a requirement to run opencode I would like to support nushell as default for windows because it is kinda like POSIX shell bash, zsh. I very tired of telling llm to run cmd every time it's trying to run bash command on cmd shell. IDK but when use on Windows (not in wsl) it only run cmd command. No offense but powershell and cmd syntax gonna take me miles before even understand what it actually does.

yindo commented

@NSPC911 commented on GitHub (Oct 14, 2025):

^ yeah, it fails to open files, list or just do things in general because commands used are posix commands that do not work on windows. either powershell is used, or cmd should be used. git bash or wsl is fine, but it shouldnt be a requirement to run opencode

I would like to support nushell as default for windows because it is kinda like POSIX shell bash, zsh. I very tired of telling llm to run cmd every time it's trying to run bash command on cmd shell. IDK but when use on Windows (not in wsl) it only run cmd command. No offense but powershell and cmd syntax gonna take me miles before even understand what it actually does.

nushell is barely posix, I wouldn't even consider it as such, many syntax that nushell makes use of doesn't work on posix shells
and anyways, should opencode require nushell to run?

@NSPC911 commented on GitHub (Oct 14, 2025): > > ^ yeah, it fails to open files, list or just do things in general because commands used are posix commands that do not work on windows. either powershell is used, or cmd should be used. git bash or wsl is fine, but it shouldnt be a requirement to run opencode > > I would like to support nushell as default for windows because it is kinda like POSIX shell bash, zsh. I very tired of telling llm to run cmd every time it's trying to run bash command on cmd shell. IDK but when use on Windows (not in wsl) it only run cmd command. No offense but powershell and cmd syntax gonna take me miles before even understand what it actually does. nushell is barely posix, I wouldn't even consider it as such, many syntax that nushell makes use of doesn't work on posix shells and anyways, should opencode require nushell to run?

yindo commented

@nielpattin commented on GitHub (Oct 14, 2025):

nushell is barely posix, I wouldn't even consider it as such, many syntax that nushell makes use of doesn't work on posix shells and anyways, should opencode require nushell to run?

opencode does require fzf, rg... I mean, maybe even better is that we can configure the shell.
So user can choose whatever they want to use, and fallback as default base on system if not found... just a suggestion.

@nielpattin commented on GitHub (Oct 14, 2025): > nushell is barely posix, I wouldn't even consider it as such, many syntax that nushell makes use of doesn't work on posix shells and anyways, should opencode require nushell to run? opencode does require fzf, rg... I mean, maybe even better is that we can configure the shell. So user can choose whatever they want to use, and fallback as default base on system if not found... just a suggestion.

yindo commented

@rekram1-node commented on GitHub (Oct 14, 2025):

opencode does require fzf, rg

@nielpattin shouldn't require you to have them preinstalled, opencode should be resolving these automatically if they aren't present on your system

@rekram1-node commented on GitHub (Oct 14, 2025): > opencode does require fzf, rg @nielpattin shouldn't require you to have them preinstalled, opencode should be resolving these automatically if they aren't present on your system

yindo commented

@nielpattin commented on GitHub (Oct 14, 2025):

opencode does require fzf, rg

@nielpattin shouldn't require you to have them preinstalled, opencode should be resolving these automatically if they aren't present on your system

I can see that they download it if it doesn't exist. But yeh. since powershell and cmd already default installed on Windows, nushell just a suggestion as it doesn't like posix but at least it is kinda like in some way.

And the original problem from Derjyn can either have to do internal code of opencode or just tell the llm to know it's in Windows environment and use cmd command instead of trying to run posix command.

Wait, are we talking about the command that AI trying to run or @Derjyn I misunderstand something?

@nielpattin commented on GitHub (Oct 14, 2025): > > opencode does require fzf, rg > > [@nielpattin](https://github.com/nielpattin) shouldn't require you to have them preinstalled, opencode should be resolving these automatically if they aren't present on your system I can see that they download it if it doesn't exist. But yeh. since powershell and cmd already default installed on Windows, nushell just a suggestion as it doesn't like posix but at least it is kinda like in some way. And the original problem from Derjyn can either have to do internal code of opencode or just tell the llm to know it's in Windows environment and use cmd command instead of trying to run posix command. Wait, are we talking about the command that AI trying to run or @Derjyn I misunderstand something?

yindo commented

@JosXa commented on GitHub (Oct 14, 2025):

^ yeah, it fails to open files, list or just do things in general because commands used are posix commands that do not work on windows. either powershell is used, or cmd should be used. git bash or wsl is fine, but it shouldnt be a requirement to run opencode

I would like to support nushell as default for windows because it is kinda like POSIX shell bash, zsh. I very tired of telling llm to run cmd every time it's trying to run bash command on cmd shell. IDK but when use on Windows (not in wsl) it only run cmd command. No offense but powershell and cmd syntax gonna take me miles before even understand what it actually does.

The only problem is that LLMs are generally terrible at producing valid NuShell syntax :/ I love it, but not with AI.
If you have a different experience, please name what models work for you :)

@JosXa commented on GitHub (Oct 14, 2025): > > ^ yeah, it fails to open files, list or just do things in general because commands used are posix commands that do not work on windows. either powershell is used, or cmd should be used. git bash or wsl is fine, but it shouldnt be a requirement to run opencode > > I would like to support nushell as default for windows because it is kinda like POSIX shell bash, zsh. I very tired of telling llm to run cmd every time it's trying to run bash command on cmd shell. IDK but when use on Windows (not in wsl) it only run cmd command. No offense but powershell and cmd syntax gonna take me miles before even understand what it actually does. The only problem is that LLMs are generally terrible at producing valid NuShell syntax :/ I love it, but not with AI. If you have a different experience, please name what models work for you :)

yindo commented

@nielpattin commented on GitHub (Oct 15, 2025):

The only problem is that LLMs are generally terrible at producing valid NuShell syntax :/ I love it, but not with AI. If you have a different experience, please name what models work for you :)

I mean, llm is generally terrible at everything if it outdated. powershell and cmd already on internet since birth, but sometimes it still gives me "no command", "xyz not exist", ...

nu is new and some command might not work, but look at this what nu give you for some basic command.

I can't cover all the case but if the llm have access to web search or have good instruction it can still do the same as cmd and powershell.

There is like 80% (I make it up) case no one will run same command line commands. So we can't just "translated command from Unix like systems to Windows" This is not something that opencode can just cover in a day or two, because there is like 1000 things different between Windows and Unix (wish they could just be use the same thing). Even on Unix systems, some time llm can't just run this posix command and working out of a box and can only work 80% of a time. It failed, but it can retry until it work.

So if we have something that llm failed to run and always want the llm run the command exact like what we want, then we can just put it in the AGENTS.md. Maybe someone have better idea in the future, but now we stuck at this. Cheer mate!

@nielpattin commented on GitHub (Oct 15, 2025): > The only problem is that LLMs are generally terrible at producing valid NuShell syntax :/ I love it, but not with AI. If you have a different experience, please name what models work for you :) I mean, llm is generally terrible at everything if it outdated. powershell and cmd already on internet since birth, but sometimes it still gives me "no command", "xyz not exist", ... nu is new and some command might not work, but look at this what nu give you for some basic command. <img width="1287" height="411" alt="Image" src="https://github.com/user-attachments/assets/8f84958e-df4e-4a47-a1c3-111eb3c83fd3" /> I can't cover all the case but if the llm have access to web search or have good instruction it can still do the same as cmd and powershell. There is like 80% (I make it up) case no one will run same command line commands. So we can't just "translated command from Unix like systems to Windows" This is not something that opencode can just cover in a day or two, because there is like 1000 things different between Windows and Unix (wish they could just be use the same thing). Even on Unix systems, some time llm can't just run this posix command and working out of a box and can only work 80% of a time. It failed, but it can retry until it work. So if we have something that llm failed to run and always want the llm run the command exact like what we want, then we can just put it in the AGENTS.md. Maybe someone have better idea in the future, but now we stuck at this. Cheer mate!

yindo commented

@Derjyn commented on GitHub (Oct 17, 2025):

That is certainly a workaround for now, but we should be aware that every such workaround eats up more tokens and such. As with all things, efficiency, tactical prompting and setup comes into play... but these platforms/tools (as in OpenCode) exist as a convenience and should be solving these issues for users in an optimal way. If they capture a user base and then stop caring about taking responsibility for these issues and push it off onto the users, well... we should just be aware. That might seem dramatic, but it really is a thing. Unless my understanding of what purpose these platforms serve is skewed 😅

I tend to add stuff to AGENTS.md or other controlling configuration files like "Environment is Windows based, so use relevant commands, tools, and operations", but that doesn't always guarantee smooth operation and we can still see wasted gas. What is a bit confounding, is that things run smoothly in a Unix-centric workflow - no issues with commands and such. So the awareness/contextual functionality for specific operating systems and environments isn't some impossible boss, but rather things seem to be hardcoded to favor Unix and be derpy with Windows.

If this issue could be tackled, and hopefully it's an easy win, I feel like the general UX and public receipt of OpenCode would be more positive. That is, you'd see less review/comparison videos where friction was pointed out. That may be out of context, but if people were being honest, that type of thing does matter.

@Derjyn commented on GitHub (Oct 17, 2025): That is certainly a workaround for now, but we should be aware that every such workaround eats up more tokens and such. As with all things, efficiency, tactical prompting and setup comes into play... but these platforms/tools (as in OpenCode) exist as a convenience and should be solving these issues for users in an optimal way. If they capture a user base and then stop caring about taking responsibility for these issues and push it off onto the users, well... we should just be aware. That might seem dramatic, but it really is a thing. Unless my understanding of what purpose these platforms serve is skewed 😅 I tend to add stuff to AGENTS.md or other controlling configuration files like "_Environment is Windows based, so use relevant commands, tools, and operations_", but that doesn't always guarantee smooth operation and we can still see wasted gas. What is a bit confounding, is that things run smoothly in a Unix-centric workflow - no issues with commands and such. So the awareness/contextual functionality for specific operating systems and environments isn't some impossible boss, but rather things seem to be hardcoded to favor Unix and be derpy with Windows. If this issue could be tackled, and hopefully it's an easy win, I feel like the general UX and public receipt of OpenCode would be more positive. That is, you'd see less review/comparison videos where friction was pointed out. That may be out of context, but if people were being honest, that type of thing _does_ matter.

yindo commented

@akierum commented on GitHub (Oct 17, 2025):

2025 we use command prompt ? to use Ai, What next ? seriously you get away to this nonsense only because coders tolerate it. Make proper install binary.

@akierum commented on GitHub (Oct 17, 2025): 2025 we use command prompt ? to use Ai, What next ? seriously you get away to this nonsense only because coders tolerate it. Make proper install binary.

yindo commented

@Derjyn commented on GitHub (Oct 18, 2025):

@akierum - I think you may be confused about what's going on. Most people using these sorts of platforms and tools live in the terminal... This might not be your cup of tea. Perhaps a web-based UI on main platforms like ChatGPT, Gemini or Claude would be more your style (or Ollama for example, now has a desktop application with a friendly UI).

Your message is like going to a car show, and yelling into the crowd "Really? CARS?! Pfft. Apparently you've never heard of an 'airplane'?". It's strange and a bit antagonistic. Or maybe there is some sort of language barrier, in which case... hey, it happens!

At any rate, this issue thread is related to general Windows support scenarios with OpenCode (which is running in a TUI/CLI, what you'd call the command prompt). Let's do our best to keep the subject matter focused, to make it easy to work on resolutions.

@Derjyn commented on GitHub (Oct 18, 2025): @akierum - I think you may be confused about what's going on. Most people using these sorts of platforms and tools live in the terminal... This might not be your cup of tea. Perhaps a web-based UI on main platforms like ChatGPT, Gemini or Claude would be more your style (or Ollama for example, now has a desktop application with a friendly UI). Your message is like going to a car show, and yelling into the crowd "Really? CARS?! Pfft. Apparently you've never heard of an 'airplane'?". It's strange and a bit antagonistic. Or maybe there is some sort of language barrier, in which case... hey, it happens! At any rate, this issue thread is related to general Windows support scenarios with OpenCode (which is running in a TUI/CLI, what you'd call the command prompt). Let's do our best to keep the subject matter focused, to make it easy to work on resolutions.

yindo commented

@Red007Master commented on GitHub (Oct 18, 2025):

2025 we use command prompt ? to use Ai, What next ? seriously you get away to this nonsense only because coders tolerate it. Make proper install binary.

You on Reddit bro, thank you for making me laugh!

@Red007Master commented on GitHub (Oct 18, 2025): > 2025 we use command prompt ? to use Ai, What next ? seriously you get away to this nonsense only because coders tolerate it. Make proper install binary. You on Reddit bro, thank you for making me laugh!

yindo commented

@JosXa commented on GitHub (Oct 18, 2025):

Can someone confirm that pasting multi-line snippets into Windows Terminal just queues individual messages, circumventing the [pasted #1 N lines] hook?

@JosXa commented on GitHub (Oct 18, 2025): Can someone confirm that pasting multi-line snippets into Windows Terminal just queues individual messages, circumventing the `[pasted #1 N lines]` hook?

yindo commented

@akierum commented on GitHub (Oct 18, 2025):

2025 we use command prompt ? to use Ai, What next ? seriously you get away to this nonsense only because coders tolerate it. Make proper install binary.

You on Reddit bro, thank you for making me laugh!

Good that you understood the joke, sarcasm whatever. Seriously I remember 1995 when PC did not start without proper autoexec.bat file and other config files for memory etc. Even then there was no Linux sudo cult and endless dependencies. I thought Linux was great too, but since dependency was not solved on 20 Years I quit. No binary, with GUI -> nonsense. I appreciate strengths of terminal as additional automation tool, but certainly not main way to operate program.

If there would be no internet (I remember those days) then Linux would be dead. Nowhere to download dependencies or get help online instantly. This Linux is not OS, it is wasteland of code. Same goes for terminal, I have wasted enough time on in in early days.

@akierum commented on GitHub (Oct 18, 2025): > > 2025 we use command prompt ? to use Ai, What next ? seriously you get away to this nonsense only because coders tolerate it. Make proper install binary. > > You on Reddit bro, thank you for making me laugh! Good that you understood the joke, sarcasm whatever. Seriously I remember 1995 when PC did not start without proper autoexec.bat file and other config files for memory etc. Even then there was no Linux sudo cult and endless dependencies. I thought Linux was great too, but since dependency was not solved on 20 Years I quit. No binary, with GUI -> nonsense. I appreciate strengths of terminal as additional automation tool, but certainly not main way to operate program. If there would be no internet (I remember those days) then Linux would be dead. Nowhere to download dependencies or get help online instantly. This Linux is not OS, it is wasteland of code. Same goes for terminal, I have wasted enough time on in in early days.

yindo commented

@Red007Master commented on GitHub (Oct 18, 2025):

2025 we use command prompt ? to use Ai, What next ? seriously you get away to this nonsense only because coders tolerate it. Make proper install binary.

You on Reddit bro, thank you for making me laugh!

Good that you understood the joke, sarcasm whatever. Seriously I remember 1995 when PC did not start without proper autoexec.bat file and other config files for memory etc. Even then there was no Linux sudo cult and endless dependencies. I thought Linux was great too, but since dependency was not solved on 20 Years I quit. No binary, with GUI -> nonsense. I appreciate strengths of terminal as additional automation tool, but certainly not main way to operate program.

If there would be no internet (I remember those days) then Linux would be dead. Nowhere to download dependencies or get help online instantly. This Linux is not OS, it is wasteland of code. Same goes for terminal, I have wasted enough time on in in early days.

I meant it like "you funny" and don't "I agree with you", don't get me wrong.

Like, you are wrong, you are literally complaining about this under open-source dev-oriented tool.
Not even talking about your point in vacuum.

Go implement GUI if you want it so much, nobody is stopping you. (or pay somebody if you want, I'm sure there are people who will do it if you can pay for it right amount)

And based on your second paragraph I can see that you yourself don't consider it to be "the joke" nor "sarcasm".

If there would be no internet (I remember those days) then Linux would be dead.

Strange, bassless, hypothetical statement. And I don't even understand what you are trying to prove or state and how is it even related to "question in question".

@Red007Master commented on GitHub (Oct 18, 2025): > > > 2025 we use command prompt ? to use Ai, What next ? seriously you get away to this nonsense only because coders tolerate it. Make proper install binary. > > > > > > You on Reddit bro, thank you for making me laugh! > > Good that you understood the joke, sarcasm whatever. Seriously I remember 1995 when PC did not start without proper autoexec.bat file and other config files for memory etc. Even then there was no Linux sudo cult and endless dependencies. I thought Linux was great too, but since dependency was not solved on 20 Years I quit. No binary, with GUI -> nonsense. I appreciate strengths of terminal as additional automation tool, but certainly not main way to operate program. > > If there would be no internet (I remember those days) then Linux would be dead. Nowhere to download dependencies or get help online instantly. This Linux is not OS, it is wasteland of code. Same goes for terminal, I have wasted enough time on in in early days. I meant it like "you funny" and don't "I agree with you", don't get me wrong. Like, you are wrong, you are literally complaining about this under open-source dev-oriented tool. Not even talking about your point in vacuum. Go implement GUI if you want it so much, nobody is stopping you. (or pay somebody if you want, I'm sure there are people who will do it if you can pay for it right amount) And based on your second paragraph I can see that you yourself don't consider it to be **"the joke"** nor **"sarcasm"**. > If there would be no internet (I remember those days) then Linux would be dead. Strange, bassless, hypothetical statement. And I don't even understand what you are trying to prove or state and how is it even related to "question in question".

yindo commented

@JosXa commented on GitHub (Oct 19, 2025):

@thdxr This thread is going off-topic quickly. Can you keep an overview over what needs doing with all this noise? Perhaps having a single ticket with all Windows issues bundled isn't the way to go 🤔

@JosXa commented on GitHub (Oct 19, 2025): @thdxr This thread is going off-topic quickly. Can you keep an overview over what needs doing with all this noise? Perhaps having a single ticket with all Windows issues bundled isn't the way to go 🤔

yindo commented

@rekram1-node commented on GitHub (Oct 19, 2025):

Ill try to clean this up some when I get a chance

@rekram1-node commented on GitHub (Oct 19, 2025): Ill try to clean this up some when I get a chance

yindo commented

@Derjyn commented on GitHub (Oct 20, 2025):

Maybe a Windows tag or template for Windows issues could be whipped up, and then parse what's here and migrate them into specific tickets. Monolithic issue threads are okay for small projects internally where you can keep things on the rails, but public repos rarely stay on track.

Apologies for contributing at all - I was attempting to get it back on track with those replies that got hidden. Totally understand the moderation actions though!

Back to the Windows support stuff: I've tinkered with more models and more terminals, and I still saw common issues popping up concerning OS dependent commands. It is somewhat simple enough to overcome this with agent/system prompts (as has been touched on) that put explicit importance on the OS. A dirty example:

CRITICAL: Tasks and projects are being developed in a Windows environment - it is
imperative that any commands and system utilities are compatible with this
environment setup, where relevant.

Now even with this in play (and other efforts layered on top), there are more than enough occasions where a Unix command is used when an agent is going at it, to call this an actual issue. I'm going to do my best to carve out time to pour over the source code out of curiosity and to see if I can catch an obvious root cause.

I'm still quite new to OpenCode, and have no qualms with the idea that it's me being naive and falling into a trap of non-evidence; while I've hammered away at un-scientific testing, these command choices by the various models/agents could simply be coincidence and poor prompting and configuration on our part. The only reason I lean toward OpenCode being the culprit, is that I've run the same lazy tests in other tools, and the Windows environment specificity is respected.

@Derjyn commented on GitHub (Oct 20, 2025): Maybe a Windows tag or template for Windows issues could be whipped up, and then parse what's here and migrate them into specific tickets. Monolithic issue threads are okay for small projects internally where you can keep things on the rails, but public repos rarely stay on track. Apologies for contributing at all - I was attempting to get it back on track with those replies that got hidden. Totally understand the moderation actions though! _Back to the Windows support stuff_: I've tinkered with more models and more terminals, and I still saw common issues popping up concerning OS dependent commands. It is somewhat simple enough to overcome this with agent/system prompts (_as has been touched on_) that put explicit importance on the OS. A dirty example: ``` CRITICAL: Tasks and projects are being developed in a Windows environment - it is imperative that any commands and system utilities are compatible with this environment setup, where relevant. ``` Now even with this in play (_and other efforts layered on top_), there are more than enough occasions where a Unix command is used when an agent is going at it, to call this an actual issue. I'm going to do my best to carve out time to pour over the source code out of curiosity and to see if I can catch an obvious root cause. I'm still quite new to OpenCode, and have no qualms with the idea that it's me being naive and falling into a trap of non-evidence; while I've hammered away at un-scientific testing, these command choices by the various models/agents could simply be coincidence and poor prompting and configuration on our part. The only reason I lean toward OpenCode being the culprit, is that I've run the same lazy tests in other tools, and the Windows environment specificity is respected.

yindo commented

@NSPC911 commented on GitHub (Oct 20, 2025):

i have a feeling that opencode sometimes still uses unix commands under the hood. some time ago, you cant attach files using the @<file> thing, but it got fixed recently. there definitely are a couple other commands and those might need fixing.

also about the labels, I think that instead of labels, github's parent and child issue feature could be used, so everything can be connected to this issue. it also looks a lot nicer because you get to see how many issues were completed related to windows

@NSPC911 commented on GitHub (Oct 20, 2025): i have a feeling that opencode sometimes still uses unix commands under the hood. some time ago, you cant attach files using the `@<file>` thing, but it got fixed recently. there definitely are a couple other commands and those might need fixing. also about the labels, I think that instead of labels, github's parent and child issue feature could be used, so everything can be connected to this issue. it also looks a lot nicer because you get to see how many issues were completed related to windows

yindo commented

@Derjyn commented on GitHub (Oct 20, 2025):

The parent/child approach is a good idea, and I need to remember that is a thing for my own endeavors as well.

I'm still digging around here and there, and so far I have found some internals that seem to add more weight toward OpenCode contributing to the not cross-platform approach. Taking a look at the files in packages/opencode/src/session/prompt, pretty much any command execution related language is Unix centric. Bash this, bash that. Having a foundation of "bash" for most all command related topics... well I can't help but think that would bedazzle any model being used into thinking from a Unix/Linux point of view right off the rip.

Again, I've only just begun to scratch the surface with OpenCode, so I could be barking up the wrong tree. However, seeing those prompts reminded me of why this topic was so important to me, personally: the desire for a clean foundation and optimal starting context/prompt scenario is incredibly important.

I'm not exactly sure what purpose those prompt text files serve outside the obvious, but it made one thing clearer to me: there isn't exactly a solid style or acute standard fleshed out there. While specific models and systems (as in Claude, Gemini, Codex, Qwen, etc) have their nuances, the wide variety of grammar, structure, and tone seems erratic to me. Not bad, like incorrect or anything - just not professional, objective and following a recognizable structure that would present glass smooth starting point for our agent setup.

And that quasi-chaotic prompt stack (wondering if this was harvested from elsewhere, and no one got around to cleaning it up?) has bits that are most certainly not cross-platform (I'm going to start saying platform-agnostic):

Here is useful information about the environment you are running in:
<env>
Working directory: /home/thdxr/dev/projects/sst/opencode/packages/opencode
Is directory a git repo: Yes
Platform: linux
OS Version: Linux 6.12.4-arch1-1
Today's date: 2025-09-30
</env>

With elements like that rattling around in the foundation, it would make sense that we'd see an unpredictable occurrence of bash commands instead of Windows command line commands. I'm always learning new best-practices and doing my best to unlearn old bad-practices, so if I misunderstood all this, by all means slap me in the head with some wisdom.

I've read that initial prompts and early words in system messages and such have more weight in setting the tone and "mindset" of agents/models, so I'm also thinking this is why even with the aforementioned overriding prompts some of us have pointed out are hit-or-miss. An agent may pay attention to the OS/dev environment we specify, other times it might be stubborn due to context size or simply the random context in play. Just a working theory I wanted to share...

Would I be on the right track to assume that if we cleaned up those core prompt files, we might see better performance across platforms?

@Derjyn commented on GitHub (Oct 20, 2025): The parent/child approach is a good idea, and I need to remember that is _a thing_ for my own endeavors as well. I'm still digging around here and there, and so far I have found some internals that seem to add more weight toward OpenCode contributing to the _not_ cross-platform approach. Taking a look at the files in <a href="https://github.com/sst/opencode/tree/dev/packages/opencode/src/session/prompt" target="_blank">`packages/opencode/src/session/prompt`</a>, pretty much any command execution related language is Unix centric. Bash this, bash that. Having a foundation of "bash" for most all command related topics... well I can't help but think that would bedazzle _any_ model being used into thinking from a Unix/Linux point of view right off the rip. Again, I've only just begun to scratch the surface with OpenCode, so I could be barking up the wrong tree. However, seeing those prompts reminded me of why this topic was so important to me, personally: the desire for a clean foundation and optimal starting context/prompt scenario is incredibly important. I'm not exactly sure what purpose those prompt text files serve outside the obvious, but it made one thing clearer to me: there isn't exactly a solid style or acute standard fleshed out there. While specific models and systems (_as in Claude, Gemini, Codex, Qwen, etc_) have their nuances, the wide variety of grammar, structure, and tone seems erratic to me. Not bad, like incorrect or anything - just not professional, objective and following a recognizable structure that would present glass smooth starting point for our agent setup. And that quasi-chaotic prompt stack (_wondering if this was harvested from elsewhere, and no one got around to cleaning it up?_) has bits that are most certainly *not* cross-platform (_I'm going to start saying platform-agnostic_): ``` Here is useful information about the environment you are running in: <env> Working directory: /home/thdxr/dev/projects/sst/opencode/packages/opencode Is directory a git repo: Yes Platform: linux OS Version: Linux 6.12.4-arch1-1 Today's date: 2025-09-30 </env> ``` With elements like that rattling around in the foundation, it would make sense that we'd see an unpredictable occurrence of bash commands instead of Windows command line commands. I'm always learning new best-practices and doing my best to unlearn old bad-practices, so if I misunderstood all this, by all means slap me in the head with some wisdom. I've read that initial prompts and early words in system messages and such have more weight in setting the tone and "mindset" of agents/models, so I'm also thinking this is why even with the aforementioned overriding prompts some of us have pointed out are hit-or-miss. An agent may pay attention to the OS/dev environment we specify, other times it might be stubborn due to context size or simply the random context in play. Just a working theory I wanted to share... Would I be on the right track to assume that if we cleaned up those core prompt files, we might see better performance across platforms?

yindo commented

@NSPC911 commented on GitHub (Oct 20, 2025):

I'm still digging around here and there, and so far I have found some internals that seem to add more weight toward OpenCode contributing to the not cross-platform approach. Taking a look at the files in packages/opencode/src/session/prompt, pretty much any command execution related language is Unix centric. Bash this, bash that. Having a foundation of "bash" for most all command related topics... well I can't help but think that would bedazzle any model being used into thinking from a Unix/Linux point of view right off the rip.

that is true, doing a search in that area https://github.com/search?q=repo%3Asst%2Fopencode+path%3A%2F%5Epackages%5C%2Fopencode%5C%2Fsrc%5C%2Fsession%5C%2Fprompt%5C%2F%2F+powershell&type=code only yields to gpt-5 for copilot, which cant be used as well as a couple other models

@NSPC911 commented on GitHub (Oct 20, 2025): > I'm still digging around here and there, and so far I have found some internals that seem to add more weight toward OpenCode contributing to the not cross-platform approach. Taking a look at the files in [packages/opencode/src/session/prompt](https://github.com/sst/opencode/tree/dev/packages/opencode/src/session/prompt?rgh-link-date=2025-10-20T11%3A12%3A29.000Z), pretty much any command execution related language is Unix centric. Bash this, bash that. Having a foundation of "bash" for most all command related topics... well I can't help but think that would bedazzle any model being used into thinking from a Unix/Linux point of view right off the rip. that is true, doing a search in that area https://github.com/search?q=repo%3Asst%2Fopencode+path%3A%2F%5Epackages%5C%2Fopencode%5C%2Fsrc%5C%2Fsession%5C%2Fprompt%5C%2F%2F+powershell&type=code only yields to gpt-5 **for copilot**, which cant be used as well as a couple other models <img width="875" height="749" alt="Image" src="https://github.com/user-attachments/assets/78786d91-9851-41e8-9d80-c438ccb986bc" />

yindo commented

@rekram1-node commented on GitHub (Oct 20, 2025):

@NSPC911 if you are getting requested model is not supported errors it is most likely for one of the following reasons:

you didnt enable the model in your copilot settings
it is a model that you dont have access to due to your subscription tier

also i like ur idea about parent child issues ill try to set that up today

@rekram1-node commented on GitHub (Oct 20, 2025): @NSPC911 if you are getting requested model is not supported errors it is most likely for one of the following reasons: 1. you didnt enable the model in your copilot settings 2. it is a model that you dont have access to due to your subscription tier also i like ur idea about parent child issues ill try to set that up today

yindo commented

@NSPC911 commented on GitHub (Oct 20, 2025):

@NSPC911 if you are getting requested model is not supported errors it is most likely for one of the following reasons:
1. you didnt enable the model in your copilot settings

ah! no wonder, it works now, thanks!

@NSPC911 commented on GitHub (Oct 20, 2025): > [@NSPC911](https://github.com/NSPC911) if you are getting requested model is not supported errors it is most likely for one of the following reasons: > > 1. you didnt enable the model in your copilot settings ah! no wonder, it works now, thanks!

yindo commented

@rekram1-node commented on GitHub (Oct 21, 2025):

Linked a bunch of sub issues, anything missing feel free to open an issue and ill link it

@rekram1-node commented on GitHub (Oct 21, 2025): Linked a bunch of sub issues, anything missing feel free to open an issue and ill link it

yindo commented

@CarlosGtrz commented on GitHub (Oct 21, 2025):

There are some PRs like: #3155, #2861

@CarlosGtrz commented on GitHub (Oct 21, 2025): There are some PRs like: #3155, #2861

yindo commented

@rekram1-node commented on GitHub (Oct 21, 2025):

Ill check them out, thanks

@rekram1-node commented on GitHub (Oct 21, 2025): Ill check them out, thanks

yindo commented

@NSPC911 commented on GitHub (Oct 21, 2025):

i think that some of the tui related issues could be fixed if opencode doesn't autoupdate while running portable (like via scoop) or through package managers (bun, npm)

@NSPC911 commented on GitHub (Oct 21, 2025): i think that some of the tui related issues could be fixed if opencode doesn't autoupdate while running portable (like via scoop) or through package managers (bun, npm)

yindo commented

@bogorad commented on GitHub (Oct 22, 2025):

hangs under win11/arm as of version 0.15.13 (used to work before, I might have missed a couple of versions on my arm64 win11 laptop), installed via scoop. shows up both in scoop and in npm. when I start, it shows nothing. but hitting ctrl+c asks if I want to terminate the batch file. looks like it fails to start.

tried under ms-terminal-preview.

@bogorad commented on GitHub (Oct 22, 2025): hangs under win11/arm as of version `0.15.13` (used to work before, I might have missed a couple of versions on my arm64 win11 laptop), installed via scoop. shows up both in scoop and in npm. when I start, it shows nothing. but hitting `ctrl+c` asks if I want to terminate the batch file. looks like it fails to start. tried under ms-terminal-preview.

yindo commented

@JosXa commented on GitHub (Oct 22, 2025):

@rekram1-node #3343

@JosXa commented on GitHub (Oct 22, 2025): @rekram1-node #3343

yindo commented

@nielpattin commented on GitHub (Oct 28, 2025):

Idk if anyone tried yet, but on Windows, assuming most people download "Git for windows"
It comes with the bash.exe
I tried to set the SHELL env to the bash.exe path, and now opencode when on Windows will use this instead of cmd.
I tested this and the LLM kinda happy with it because the LLm always tried to run "posix" command.

@nielpattin commented on GitHub (Oct 28, 2025): Idk if anyone tried yet, but on Windows, assuming most people download "Git for windows" It comes with the bash.exe I tried to set the SHELL env to the bash.exe path, and now opencode when on Windows will use this instead of cmd. I tested this and the LLM kinda happy with it because the LLm always tried to run "posix" command. <img width="449" height="54" alt="Image" src="https://github.com/user-attachments/assets/e4d20e41-b6b6-4684-ba2f-72f426cf70ee" />

yindo commented

@heditwo commented on GitHub (Oct 31, 2025):

https://github.com/user-attachments/assets/2f2bceb2-1e27-4b92-be62-d542daf7809f
On Windows via WezTerm terminal, text selection does not work. I've attached a video of the issue in action

I am currently on pwsh version 5.1

`
Major Minor Build Revision

5 1 19041 6456
`

This issue only happens on the opentui branch/1.0.0 release branch.

Congrats again on the 1.0.0 release, and thanks for all the hard work you guys have put into this tool

@heditwo commented on GitHub (Oct 31, 2025): https://github.com/user-attachments/assets/2f2bceb2-1e27-4b92-be62-d542daf7809f On Windows via WezTerm terminal, text selection does not work. I've attached a video of the issue in action I am currently on pwsh version 5.1 ` Major Minor Build Revision ----- ----- ----- -------- 5 1 19041 6456 ` This issue only happens on the opentui branch/1.0.0 release branch. Congrats again on the 1.0.0 release, and thanks for all the hard work you guys have put into this tool

yindo commented

@RichardScottOZ commented on GitHub (Nov 2, 2025):

Idk if anyone tried yet, but on Windows, assuming most people download "Git for windows" It comes with the bash.exe I tried to set the SHELL env to the bash.exe path, and now opencode when on Windows will use this instead of cmd. I tested this and the LLM kinda happy with it because the LLm always tried to run "posix" command.

I tried multiple variants of this with no luck - is this a personal or corporate machine? (my problem)

@RichardScottOZ commented on GitHub (Nov 2, 2025): > Idk if anyone tried yet, but on Windows, assuming most people download "Git for windows" It comes with the bash.exe I tried to set the SHELL env to the bash.exe path, and now opencode when on Windows will use this instead of cmd. I tested this and the LLM kinda happy with it because the LLm always tried to run "posix" command. > <img alt="Image" width="449" height="54" src="https://private-user-images.githubusercontent.com/66520542/506464277-e4d20e41-b6b6-4684-ba2f-72f426cf70ee.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjIxMzQ0ODEsIm5iZiI6MTc2MjEzNDE4MSwicGF0aCI6Ii82NjUyMDU0Mi81MDY0NjQyNzctZTRkMjBlNDEtYjZiNi00Njg0LWJhMmYtNzJmNDI2Y2Y3MGVlLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTExMDMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUxMTAzVDAxNDMwMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTM1YTY1YjBjYTgyNDI5NzgwMWI1MzNhNGFiMzU5YjlmNTFmNGYxN2E3ZGIyZjY4ZDEzMmY2YjBjMmQ0MjdmYTkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.ysLucxvz35JF9GYy86yVCVlbQgy6PbYzW92CcAW2a7w"> I tried multiple variants of this with no luck - is this a personal or corporate machine? (my problem)

yindo commented

@Derjyn commented on GitHub (Nov 3, 2025):

Idk if anyone tried yet, but on Windows, assuming most people download "Git for windows" It comes with the bash.exe I tried to set the SHELL env to the bash.exe path, and now opencode when on Windows will use this instead of cmd. I tested this and the LLM kinda happy with it because the LLm always tried to run "posix" command.

I tried multiple variants of this with no luck - is this a personal or corporate machine? (my problem)

Do you mean you were having trouble finding the executable, or getting an agent to play nice and use that specific executable? If it's an issue with the executable:

Download/install Git For Windows
Executable path will be: /install-directory/Git/bin/bash.exe

If it's an issue with getting the agent to use the executable, that is a can of worms. Allow me to get into the weeds a bit (and I mean no disrespect with my words - I'm being direct and solution-seeking)...

One of the primary sources of friction I have with OpenCode, has been the hardcoded prompts that are not cross-platform. While I have a personal opinion and love/prefer Linux, I'm also objective and professional; At a foundational level, as many prompts that users cannot edit easily should be platform-agnostic.

Unfortunately some primary and highly influential prompts have been chosen that are opinionated vs objective, specifically calling out Linux as the environment and similarly commands and tool calls and have a high tendency to align agents. Thus, it currently falls on the user to overpower those prompts. I'm noticing this is the wild west right now, with many users having mixed results. I myself had a good run where I had no issue, within a Windows environment. That good run ended and I stopped trying to overpower the internal system messages, moving (back) to another solution and haven't looked back.

The lack of determinism and a clean foundation on the internal system prompts devoid of opinion is the only issue I have, but am patiently waiting for these bits and bobs to be addressed. I haven't seen any devs speak on this subject or respond clearly when it is called out, which may ultimately be a deal breaker if it's intentional. Linux is the best, we all know. So is obtaining expected results when using battle-tested approaches that work just fine in other solutions, and the cause of the difficulty is known.

All that being said, what I previously had working for me was something along the lines of the following placed in a global prompt/system message (as always, YMMV):

XML-like approach:

... other stuff ...

### CRITICAL: Development Environment
<dev_env>
  <os>Windows 11</os>
  <bash>C:\Program Files\Git\bin\bash.exe</bash>
  ... other stuff ...
</dev_env>

Basic listed approach:

... other stuff ...

### CRITICAL: Development Environment
* OS: Windows ME
* Bash executable: C:\Program Files\Git\bin\bash.exe
* ... other stuff ...

NL approach:

... other stuff ...

### CRITICAL: Development Environment
My operating system is Windows Vista - by default make sure to use compatible file types, workflows, and commands 
unless told otherwise. Similarly, when executing any bash-related commands, use the bash executable found at the 
following location: "C:\Program Files\Git\bin\bash.exe".  While it is IMPORTANT that you follow this approach, there 
are scenarios where other approaches are needed. Take a logical stance and if you aren't able to execute a command or 
run another platform's executable, DO NOT keep repeatedly attempting. Instead fall back to the defaults above.

Those are just rough examples that get the general idea across, and you may need to place even more importance (using keywords like CRITICAL, IMPORTANT, REQUIRED that many models pay attention to) on your desired values, or repeat yourself.

Another issue you may run into is context poisoning - depending on where you have these types of prompts positioned, it may get lost to an agent's whimsy among a huge context load in a session. I was placing these types of prompts towards the beginning of my system messages/agent files, etc.

Hopefully that helps, but I found it eventually too much of a battle to keep fighting, and simply can't accept wasting tokens/context for something as standard as this. I'd rather fill that context with something more useful, versus something required to function.

@Derjyn commented on GitHub (Nov 3, 2025): > _Idk if anyone tried yet, but on Windows, assuming most people download "Git for windows" It comes with the bash.exe I tried to set the SHELL env to the bash.exe path, and now opencode when on Windows will use this instead of cmd. I tested this and the LLM kinda happy with it because the LLm always tried to run "posix" command._ > I tried multiple variants of this with no luck - is this a personal or corporate machine? (my problem) Do you mean you were having trouble finding the executable, or getting an agent to play nice and use that specific executable? If it's an issue with the executable: 1. Download/install _[Git For Windows](https://gitforwindows.org/)_ 2. Executable path will be: `/install-directory/Git/bin/bash.exe` If it's an issue with getting the agent to use the executable, that is a can of worms. Allow me to get into the weeds a bit (_and I mean no disrespect with my words - I'm being direct and solution-seeking_)... --- One of the primary sources of friction I have with OpenCode, has been the hardcoded prompts that are not cross-platform. While I have a personal opinion and love/prefer Linux, I'm also objective and professional; At a foundational level, as many prompts that users cannot edit easily should be platform-agnostic. Unfortunately some primary and highly influential prompts have been chosen that are opinionated vs objective, specifically calling out Linux as the environment and similarly commands and tool calls and have a high tendency to align agents. Thus, it currently falls on the user to overpower those prompts. I'm noticing this is the wild west right now, with many users having mixed results. I myself had a good run where I had no issue, within a Windows environment. That good run ended and I stopped trying to overpower the internal system messages, moving (_back_) to another solution and haven't looked back. The lack of determinism and a clean foundation on the internal system prompts devoid of opinion is the only issue I have, but am patiently waiting for these bits and bobs to be addressed. I haven't seen any devs speak on this subject or respond clearly when it is called out, which may ultimately be a deal breaker if it's intentional. Linux is the best, we all know. So is obtaining expected results when using battle-tested approaches that work just fine in other solutions, and the cause of the difficulty is known. --- All that being said, what I previously had working for me was something along the lines of the following placed in a global prompt/system message (_as always, YMMV_): **XML-like approach:** ```markdown ... other stuff ... ### CRITICAL: Development Environment <dev_env> <os>Windows 11</os> <bash>C:\Program Files\Git\bin\bash.exe</bash> ... other stuff ... </dev_env> ``` **Basic listed approach:** ```markdown ... other stuff ... ### CRITICAL: Development Environment * OS: Windows ME * Bash executable: C:\Program Files\Git\bin\bash.exe * ... other stuff ... ``` **NL approach:** ```markdown ... other stuff ... ### CRITICAL: Development Environment My operating system is Windows Vista - by default make sure to use compatible file types, workflows, and commands unless told otherwise. Similarly, when executing any bash-related commands, use the bash executable found at the following location: "C:\Program Files\Git\bin\bash.exe". While it is IMPORTANT that you follow this approach, there are scenarios where other approaches are needed. Take a logical stance and if you aren't able to execute a command or run another platform's executable, DO NOT keep repeatedly attempting. Instead fall back to the defaults above. ``` Those are just rough examples that get the general idea across, and you may need to place even more importance (_using keywords like CRITICAL, IMPORTANT, REQUIRED that many models pay attention to_) on your desired values, or repeat yourself. Another issue you may run into is context poisoning - depending on where you have these types of prompts positioned, it may get lost to an agent's whimsy among a huge context load in a session. I was placing these types of prompts towards the beginning of my system messages/agent files, etc. Hopefully that helps, but I found it eventually too much of a battle to keep fighting, and simply can't accept wasting tokens/context for something as standard as this. I'd rather fill that context with something more useful, versus something required to function.

yindo commented

@RichardScottOZ commented on GitHub (Nov 3, 2025):

As mentioned previously, many versions of attempting to get the shell to work to get it to run at all, nothing to do with prompts downstream.

@RichardScottOZ commented on GitHub (Nov 3, 2025): As mentioned previously, many versions of attempting to get the shell to work to get it to run at all, nothing to do with prompts downstream.

yindo commented

@Derjyn commented on GitHub (Nov 3, 2025):

So then your agents can't run any bash commands at all, is what you're saying? If that's the case... then it likely is an issue in your environment. Even without all my jargon about prompting this way or that, or other approaches - basically a clean install, should have an agent able to run bash commands, even if they fail (due to referencing a non-existent executable in the call).

What does the output look like when an agent tries to run a bash command? Paste an example in here, maybe it's an easy win.

@Derjyn commented on GitHub (Nov 3, 2025): So then your agents can't run any bash commands at all, is what you're saying? If that's the case... then it likely is an issue in your environment. Even without all my jargon about prompting this way or that, or other approaches - basically a clean install, should have an agent able to run bash commands, even if they fail (_due to referencing a non-existent executable in the call_). What does the output look like when an agent tries to run a bash command? Paste an example in here, maybe it's an easy win.

yindo commented

@RichardScottOZ commented on GitHub (Nov 3, 2025):

No. Opencode does not run. See issue titled EBADF.

@RichardScottOZ commented on GitHub (Nov 3, 2025): No. Opencode does not run. See issue titled EBADF.

yindo commented

@Derjyn commented on GitHub (Nov 3, 2025):

Ah. Bad file descriptor shenanigans. Most of my experience there (IT support related, edge-cases)... it came down to permissions or borked environment setup. Are all your prereqs up to date? Node, Bun, etc? That's the last bit of self-help I can imagine, could very well be a legitimate bug with OpenCode on Windows (versus an issue on your end, with your environment). Very much a "is it plugged in" line, but I've seen plenty of scenarios where getting prereqs UTD ended up being the resolution.

@Derjyn commented on GitHub (Nov 3, 2025): Ah. Bad file descriptor shenanigans. Most of my experience there (_IT support related, edge-cases_)... it came down to permissions or borked environment setup. Are all your prereqs up to date? Node, Bun, etc? That's the last bit of self-help I can imagine, could very well be a _legitimate_ bug with OpenCode on Windows (_versus an issue on your end, with your environment_). Very much a "is it plugged in" line, but I've seen plenty of scenarios where getting prereqs UTD ended up being the resolution.

yindo commented

@RichardScottOZ commented on GitHub (Nov 3, 2025):

Yes, tried several different versions of each. Some chance it is related to 'enterprise windows shenanigans' but no chance of not 'being up to date' - apart from 'needing to install some esoteric version of node from source from 87 hours ago'. Just the usual method.

@RichardScottOZ commented on GitHub (Nov 3, 2025): Yes, tried several different versions of each. Some chance it is related to 'enterprise windows shenanigans' but no chance of not 'being up to date' - apart from 'needing to install some esoteric version of node from source from 87 hours ago'. Just the usual method.

yindo commented

@ZarK commented on GitHub (Nov 9, 2025):

Opencode worked much better for me on windows last week. Today it constantly just stops, it is "working..." but nothing happens. Just a few loops and then it hangs like this. Tried in four different terminals and tried both Zen and openrouter models.

@ZarK commented on GitHub (Nov 9, 2025): Opencode worked much better for me on windows last week. Today it constantly just stops, it is "working..." but nothing happens. Just a few loops and then it hangs like this. Tried in four different terminals and tried both Zen and openrouter models.

yindo commented

@bramburn commented on GitHub (Nov 9, 2025):

It's this sorted?

Regards,

B.Ramburn BSc (Hons) LLM MCIArb
Snr. Quantity Surveyor & Director at Icelabz

On Sun, 9 Nov 2025, 22:20 Tjalve Aarflot, @.***> wrote:

ZarK left a comment (sst/opencode#631)
https://github.com/sst/opencode/issues/631#issuecomment-3508889809

Opencode worked much better for me on windows last week. Today it
constantly just stops, it is "working..." but nothing happens. Just a few
loops and then it hangs like this. Tried in four different terminals and
tried both Zen and openrouter models.

—
Reply to this email directly, view it on GitHub
https://github.com/sst/opencode/issues/631#issuecomment-3508889809, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUTT3NBFBCL4QFNZFBD7L33364ZTAVCNFSM6AAAAACAVSP5UGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMBYHA4DSOBQHE
.
You are receiving this because you commented.Message ID:
@.***>

@bramburn commented on GitHub (Nov 9, 2025): It's this sorted? Regards, B.Ramburn BSc (Hons) LLM MCIArb Snr. Quantity Surveyor & Director at Icelabz On Sun, 9 Nov 2025, 22:20 Tjalve Aarflot, ***@***.***> wrote: > *ZarK* left a comment (sst/opencode#631) > <https://github.com/sst/opencode/issues/631#issuecomment-3508889809> > > Opencode worked much better for me on windows last week. Today it > constantly just stops, it is "working..." but nothing happens. Just a few > loops and then it hangs like this. Tried in four different terminals and > tried both Zen and openrouter models. > > — > Reply to this email directly, view it on GitHub > <https://github.com/sst/opencode/issues/631#issuecomment-3508889809>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACUTT3NBFBCL4QFNZFBD7L33364ZTAVCNFSM6AAAAACAVSP5UGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMBYHA4DSOBQHE> > . > You are receiving this because you commented.Message ID: > ***@***.***> >

yindo commented

@rekram1-node commented on GitHub (Nov 9, 2025):

@ZarK What is it doing when it is stuck in a "working" state?. What version are u on?

@rekram1-node commented on GitHub (Nov 9, 2025): @ZarK What is it doing when it is stuck in a "working" state?. What version are u on?

yindo commented

@jdwilsonjr commented on GitHub (Nov 12, 2025):

We refer to the moment opencode glitches on Windows as "Going Tetris". An homage of sorts to Spaceballs "Going plaid". Every morning I npm --global update with my coffee. Then see how long before opencode goes tetris. After which, back to business as usual with Claude or Codex or Gemini or ...

Have to say that I am delighted to see this issue pinned. There are a number of Windows users out here. Godspeed on this one.

@jdwilsonjr commented on GitHub (Nov 12, 2025): We refer to the moment opencode glitches on Windows as "Going Tetris". An homage of sorts to Spaceballs "Going plaid". Every morning I npm --global update with my coffee. Then see how long before opencode goes tetris. After which, back to business as usual with Claude or Codex or Gemini or ... Have to say that I am delighted to see this issue pinned. There are a number of Windows users out here. Godspeed on this one.

yindo commented

@bramburn commented on GitHub (Nov 12, 2025):

With all the AI out there use open code to fix it and get it working.

Regards,

B.Ramburn BSc (Hons) LLM MCIArb
Snr. Quantity Surveyor & Director at Icelabz

On Wed, 12 Nov 2025, 23:17 jdwilsonjr, @.***> wrote:

jdwilsonjr left a comment (sst/opencode#631)
https://github.com/sst/opencode/issues/631#issuecomment-3524289477

We refer to the moment opencode glitches on Windows as "Going Tetris". An
homage of sorts to Spaceballs "Going plaid". Every morning I npm --global
update with my coffee. Then see how long before opencode goes tetris. After
which, back to business as usual with Claude or Codex or Gemini or ...

Have to say that I am delighted to see this issue pinned. There are a
number of Windows users out here. Godspeed on this one.

—
Reply to this email directly, view it on GitHub
https://github.com/sst/opencode/issues/631#issuecomment-3524289477, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUTT3I7IFAV5K4GPKC7WSD34O5XDAVCNFSM6AAAAACAVSP5UGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMRUGI4DSNBXG4
.
You are receiving this because you commented.Message ID:
@.***>

@bramburn commented on GitHub (Nov 12, 2025): With all the AI out there use open code to fix it and get it working. Regards, B.Ramburn BSc (Hons) LLM MCIArb Snr. Quantity Surveyor & Director at Icelabz On Wed, 12 Nov 2025, 23:17 jdwilsonjr, ***@***.***> wrote: > *jdwilsonjr* left a comment (sst/opencode#631) > <https://github.com/sst/opencode/issues/631#issuecomment-3524289477> > > We refer to the moment opencode glitches on Windows as "Going Tetris". An > homage of sorts to Spaceballs "Going plaid". Every morning I npm --global > update with my coffee. Then see how long before opencode goes tetris. After > which, back to business as usual with Claude or Codex or Gemini or ... > > Have to say that I am delighted to see this issue pinned. There are a > number of Windows users out here. Godspeed on this one. > > — > Reply to this email directly, view it on GitHub > <https://github.com/sst/opencode/issues/631#issuecomment-3524289477>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACUTT3I7IFAV5K4GPKC7WSD34O5XDAVCNFSM6AAAAACAVSP5UGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMRUGI4DSNBXG4> > . > You are receiving this because you commented.Message ID: > ***@***.***> >

yindo commented

@Kreijstal commented on GitHub (Nov 15, 2025):

codex kinda works on windows

@Kreijstal commented on GitHub (Nov 15, 2025): codex kinda works on windows

yindo commented

@rekram1-node commented on GitHub (Nov 15, 2025):

We have a few windows updates shipping this week that should get it to a much better state for everyone.

@rekram1-node commented on GitHub (Nov 15, 2025): We have a few windows updates shipping this week that should get it to a much better state for everyone.

yindo commented

@Kreijstal commented on GitHub (Nov 16, 2025):

can you also use opencode over ssh for windows (you can use ssh from cygwin/msys2 btw)

@Kreijstal commented on GitHub (Nov 16, 2025): can you also use opencode over ssh for windows (you can use ssh from cygwin/msys2 btw)

yindo commented

@0xn3bs commented on GitHub (Nov 20, 2025):

Installed opencode using Choco.

Using the ! key to run shell commands launches wsl.exe instead of cmd.exe. Doesn't appear the underlying shell that's launched is configurable anywhere unless I'm missing something.

Screenshot of window that briefly pops up when trying to run shell commands:

@0xn3bs commented on GitHub (Nov 20, 2025): Installed opencode using Choco. Using the ! key to run shell commands launches wsl.exe instead of cmd.exe. Doesn't appear the underlying shell that's launched is configurable anywhere unless I'm missing something. Screenshot of window that briefly pops up when trying to run shell commands: <img width="625" height="352" alt="Image" src="https://github.com/user-attachments/assets/f4baeafa-1af2-4de8-ab8e-89e63872ed3f" />

yindo commented

@rekram1-node commented on GitHub (Nov 20, 2025):

@0xn3bs underlying shell is configurable using $SHELL

@rekram1-node commented on GitHub (Nov 20, 2025): @0xn3bs underlying shell is configurable using $SHELL

yindo commented

@nikitakot commented on GitHub (Nov 21, 2025):

Anyone here switched from claude code to opencode recently on native Windows? How is it? Ready?

@nikitakot commented on GitHub (Nov 21, 2025): Anyone here switched from claude code to opencode recently on native Windows? How is it? Ready?

yindo commented

@nielpattin commented on GitHub (Nov 21, 2025):

Anyone here switched from claude code to opencode recently on native Windows? How is it? Ready?

Highlighting for markdown response or diff view not there yet.
shift+enter doesn't do new line (use ctrl+j or ctrl+enter instead)
pasting is weird, paste normal text with ctrl+v is fine, ctrl+v with image is fine, but for multiple line like a json or long logs you need to use ctrl+shift+v.
opencode TUI not re-render or whatever it calls when you resize the terminal
Pasting image not working on Terminal Windows just use wezterm or alacritty.
Someone said in the discord pasting image in WSL worked now.
/exit or ctrl+c randomly close the terminal (you will getting like 80% chance it will close the terminal, and 20% it will exit quietly)
Other than that, it's fine and usable. (I would say 90%) working rn.
Team is trying to get the windows ready fast as possible and cheer on contributor on the Windows that make it possible.

@nielpattin commented on GitHub (Nov 21, 2025): > Anyone here switched from claude code to opencode recently on native Windows? How is it? Ready? 1. Highlighting for markdown response or diff view not there yet. 2. shift+enter doesn't do new line (use `ctrl+j` or `ctrl+enter` instead) 3. pasting is weird, paste normal text with `ctrl+v` is fine, `ctrl+v` with image is fine, but for multiple line like a json or long logs you need to use `ctrl+shift+v`. 4. opencode TUI not re-render or whatever it calls when you resize the terminal 5. Pasting image not working on Terminal Windows just use wezterm or alacritty. 6. Someone said in the discord pasting image in WSL worked now. 7. `/exit` or `ctrl+c` randomly close the terminal (you will getting like 80% chance it will close the terminal, and 20% it will exit quietly) 8. Other than that, it's fine and usable. (I would say 90%) working rn. 9. Team is trying to get the windows ready fast as possible and cheer on contributor on the Windows that make it possible.

yindo commented

@JosXa commented on GitHub (Nov 21, 2025):

pasting is weird, paste normal text with ctrl+v is fine, ctrl+v with image is fine, but for multiple line like a json or long logs you need to use ctrl+shift+v.

This is solved for me as of recently, praise the lord (or the dev)!

@JosXa commented on GitHub (Nov 21, 2025): > 3. pasting is weird, paste normal text with `ctrl+v` is fine, `ctrl+v` with image is fine, but for multiple line like a json or long logs you need to use `ctrl+shift+v`. This is solved for me as of recently, praise the lord (or the dev)!

yindo commented

@0xn3bs commented on GitHub (Nov 22, 2025):

Anyone here switched from claude code to OpenCode recently on native Windows? How is it? Ready?
It's working great for me. Been using it with gemini-3-pro-preview and it's great now that I have $SHELL pointing to PowerShell.

Some quirks I noticed is resizing the window really bugs it out - Claude Code suffers from a similar issue but with OpenCode it can leave it unusable. So for now, whatever size window you started OpenCode, leave it at that and don't touch it.

Sometimes quitting OpenCode will cause any mouse movement/scrolls to print symbols to the console and I'm forced to close that Powershell instance.

I'm enjoying it.

@0xn3bs commented on GitHub (Nov 22, 2025): > > Anyone here switched from claude code to OpenCode recently on native Windows? How is it? Ready? It's working great for me. Been using it with gemini-3-pro-preview and it's great now that I have $SHELL pointing to PowerShell. Some quirks I noticed is resizing the window really bugs it out - Claude Code suffers from a similar issue but with OpenCode it can leave it unusable. So for now, whatever size window you started OpenCode, leave it at that and don't touch it. Sometimes quitting OpenCode will cause any mouse movement/scrolls to print symbols to the console and I'm forced to close that Powershell instance. I'm enjoying it.

yindo commented

@NSPC911 commented on GitHub (Nov 22, 2025):

/exit or ctrl+c randomly close the terminal (you will getting like 80% chance it will close the terminal, and 20% it will exit quietly)

so it isnt just me!! #3691

@NSPC911 commented on GitHub (Nov 22, 2025): > 7. `/exit` or `ctrl+c` randomly close the terminal (you will getting like 80% chance it will close the terminal, and 20% it will exit quietly) so it isnt just me!! #3691

yindo commented

@JosXa commented on GitHub (Nov 22, 2025):

/exit or ctrl+c randomly close the terminal (you will getting like 80% chance it will close the terminal, and 20% it will exit quietly)

so it isnt just me!! #3691

First ctrl+c clears the input, y'all are aware of that?

@JosXa commented on GitHub (Nov 22, 2025): > > 7. `/exit` or `ctrl+c` randomly close the terminal (you will getting like 80% chance it will close the terminal, and 20% it will exit quietly) > > so it isnt just me!! [#3691](https://github.com/sst/opencode/issues/3691) First ctrl+c clears the input, y'all are aware of that?

yindo commented

@nielpattin commented on GitHub (Nov 22, 2025):

First ctrl+c clears the input, y'all are aware of that?

I mean ctrl+c multiple time, normally we force quit running process like that. It was working on 0.15.31 back. But after v1.0.0 it's never working again. Even using /exit do the same things. Do we need a video to showcase that?

@nielpattin commented on GitHub (Nov 22, 2025): > First ctrl+c clears the input, y'all are aware of that? I mean `ctrl+c` multiple time, normally we force quit running process like that. It was working on `0.15.31` back. But after v1.0.0 it's never working again. Even using `/exit` do the same things. Do we need a video to showcase that?

yindo commented

@JosXa commented on GitHub (Nov 22, 2025):

First ctrl+c clears the input, y'all are aware of that?

I mean ctrl+c multiple time, normally we force quit running process like that. It was working on 0.15.31 back. But after v1.0.0 it's never working again. Even using /exit do the same things. Do we need a video to showcase that?

Perhaps. At least /exit is very reliable for me

@JosXa commented on GitHub (Nov 22, 2025): > > First ctrl+c clears the input, y'all are aware of that? > > I mean `ctrl+c` multiple time, normally we force quit running process like that. It was working on `0.15.31` back. But after v1.0.0 it's never working again. Even using `/exit` do the same things. Do we need a video to showcase that? Perhaps. At least /exit is very reliable for me

yindo commented

https://github.com/user-attachments/assets/b33e4443-b079-4aa5-a68d-33200783d4a1

@nielpattin commented on GitHub (Nov 22, 2025):

Perhaps. At least /exit is very reliable for me

Yeh, perhaps I got unlucky then.

@nielpattin commented on GitHub (Nov 22, 2025): > Perhaps. At least /exit is very reliable for me Yeh, perhaps I got unlucky then. https://github.com/user-attachments/assets/b33e4443-b079-4aa5-a68d-33200783d4a1

yindo commented

@rekram1-node commented on GitHub (Nov 22, 2025):

@0xn3bs

Some quirks I noticed is resizing the window really bugs it ou

This should have been fixed in one of the latest releases, our contributor made a bug fix for bun so the resizing should work for claude code too soon

@rekram1-node commented on GitHub (Nov 22, 2025): @0xn3bs > Some quirks I noticed is resizing the window really bugs it ou This should have been fixed in one of the latest releases, our contributor made a bug fix for bun so the resizing should work for claude code too soon

yindo commented

@nikitakot commented on GitHub (Nov 22, 2025):

what's the recommended terminal app for Windows? is there something not supported in Windows Terminal?

@nikitakot commented on GitHub (Nov 22, 2025): what's the recommended terminal app for Windows? is there something not supported in Windows Terminal?

yindo commented

@bramburn commented on GitHub (Nov 22, 2025):

I use auggie, Claude code and Gemini all work well on windows.

Regards,

B.Ramburn BSc (Hons) LLM MCIArb
Snr. Quantity Surveyor & Director at Icelabz

On Sat, 22 Nov 2025, 20:34 Nikita Kot, @.***> wrote:

nikitakot left a comment (sst/opencode#631)
https://github.com/sst/opencode/issues/631#issuecomment-3567028470

what's the recommended terminal app for Windows? is there something not
supported in Windows Terminal?

—
Reply to this email directly, view it on GitHub
https://github.com/sst/opencode/issues/631#issuecomment-3567028470, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUTT3NSRK6F76TOSDZPQW336DCFDAVCNFSM6AAAAACAVSP5UGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNRXGAZDQNBXGA
.
You are receiving this because you commented.Message ID:
@.***>

@bramburn commented on GitHub (Nov 22, 2025): I use auggie, Claude code and Gemini all work well on windows. Regards, B.Ramburn BSc (Hons) LLM MCIArb Snr. Quantity Surveyor & Director at Icelabz On Sat, 22 Nov 2025, 20:34 Nikita Kot, ***@***.***> wrote: > *nikitakot* left a comment (sst/opencode#631) > <https://github.com/sst/opencode/issues/631#issuecomment-3567028470> > > what's the recommended terminal app for Windows? is there something not > supported in Windows Terminal? > > — > Reply to this email directly, view it on GitHub > <https://github.com/sst/opencode/issues/631#issuecomment-3567028470>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACUTT3NSRK6F76TOSDZPQW336DCFDAVCNFSM6AAAAACAVSP5UGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNRXGAZDQNBXGA> > . > You are receiving this because you commented.Message ID: > ***@***.***> >

yindo commented

Opencode docs: recommended terminal app

@nielpattin commented on GitHub (Nov 22, 2025):

what's the recommended terminal app for Windows? is there something not supported in Windows Terminal?

You can't paste image on Windows Terminal

For recommended, there are two terminal apps you can use on Windows rn:

@nielpattin commented on GitHub (Nov 22, 2025): > what's the recommended terminal app for Windows? is there something not supported in Windows Terminal? You can't paste image on Windows Terminal For recommended, there are two terminal apps you can use on Windows rn: [Opencode docs: recommended terminal app ](https://opencode.ai/docs#:~:text=To%20use%20OpenCode%2C%20you%E2%80%99ll%20need%3A)

yindo commented

@Thanaen commented on GitHub (Dec 8, 2025):

Sometimes quitting OpenCode will cause any mouse movement/scrolls to print symbols to the console and I'm forced to close that Powershell instance.

I'm enjoying it.

Several of us use Opencode with Git Bash or PowerShell, and this happens to us frequently.

I am NOT enjoying it 😆

@Thanaen commented on GitHub (Dec 8, 2025): > Sometimes quitting OpenCode will cause any mouse movement/scrolls to print symbols to the console and I'm forced to close that Powershell instance. > > I'm enjoying it. Several of us use Opencode with Git Bash or PowerShell, and this happens to us frequently. I am NOT enjoying it 😆 <img width="956" height="454" alt="Image" src="https://github.com/user-attachments/assets/ef9aab63-cf54-4f1e-afbd-7030c0ce1d4d" />

yindo commented

@vruss commented on GitHub (Dec 8, 2025):

Is it recommended to run opencode in gitbash or powershell or cmd when on Windows? I noticed that almost always the agents will try to use bash commands and therefor fail.

@vruss commented on GitHub (Dec 8, 2025): Is it recommended to run opencode in gitbash or powershell or cmd when on Windows? I noticed that almost always the agents will try to use bash commands and therefor fail.

yindo commented

@nielpattin commented on GitHub (Dec 9, 2025):

Is it recommended to run opencode in gitbash or powershell or cmd when on Windows? I noticed that almost always the agents will try to use bash commands and therefor fail.

You set the SHELL env on Windows to where bash.exe is from gitbash mostly from C:\Program Files\Git\bin\bash.exe

Because the llm gonna try to follow the bash rule anyway. Trust me, bash.exe from git for windows is amazing and gonna work 90% of the time instead of asking the llm to write up powershell or cmd code.

@nielpattin commented on GitHub (Dec 9, 2025): > Is it recommended to run opencode in gitbash or powershell or cmd when on Windows? I noticed that almost always the agents will try to use bash commands and therefor fail. You set the SHELL env on Windows to where bash.exe is from gitbash mostly from `C:\Program Files\Git\bin\bash.exe` Because the llm gonna try to follow the bash rule anyway. Trust me, bash.exe from git for windows is amazing and gonna work 90% of the time instead of asking the llm to write up powershell or cmd code.

yindo commented

@ajaffie commented on GitHub (Dec 9, 2025):

Anyone here switched from claude code to OpenCode recently on native Windows? How is it? Ready?
It's working great for me. Been using it with gemini-3-pro-preview and it's great now that I have $SHELL pointing to PowerShell.

Some quirks I noticed is resizing the window really bugs it out - Claude Code suffers from a similar issue but with OpenCode it can leave it unusable. So for now, whatever size window you started OpenCode, leave it at that and don't touch it.

Sometimes quitting OpenCode will cause any mouse movement/scrolls to print symbols to the console and I'm forced to close that Powershell instance.

I'm enjoying it.

This, but I can never run opencode again because I get Error: agent coder not found and it prints usage

@ajaffie commented on GitHub (Dec 9, 2025): > > > Anyone here switched from claude code to OpenCode recently on native Windows? How is it? Ready? > > > It's working great for me. Been using it with gemini-3-pro-preview and it's great now that I have $SHELL pointing to PowerShell. > > Some quirks I noticed is resizing the window really bugs it out - Claude Code suffers from a similar issue but with OpenCode it can leave it unusable. So for now, whatever size window you started OpenCode, leave it at that and don't touch it. > > Sometimes quitting OpenCode will cause any mouse movement/scrolls to print symbols to the console and I'm forced to close that Powershell instance. > > I'm enjoying it. This, but I can never run opencode again because I get `Error: agent coder not found` and it prints usage

yindo commented

@nikitakot commented on GitHub (Dec 13, 2025):

what's the best way to workaround the ctrl+c behavior on Windows rn? I want it to copy text, not to quit the cli. I'm on Windows Terminal but about to switch to WezTerm. Can I stop ctrl+c to quit opencode in WezTerm somehow?

@nikitakot commented on GitHub (Dec 13, 2025): what's the best way to workaround the ctrl+c behavior on Windows rn? I want it to copy text, not to quit the cli. I'm on Windows Terminal but about to switch to WezTerm. Can I stop ctrl+c to quit opencode in WezTerm somehow?

yindo commented

@rekram1-node commented on GitHub (Dec 13, 2025):

I shipped better defaults for shell discovery on windows it should try to find git bash better

@rekram1-node commented on GitHub (Dec 13, 2025): I shipped better defaults for shell discovery on windows it should try to find git bash better

yindo commented

@rekram1-node commented on GitHub (Dec 13, 2025):

@nikitakot to copy text its just click, drag, and release should copy for u

@rekram1-node commented on GitHub (Dec 13, 2025): @nikitakot to copy text its just click, drag, and release should copy for u

yindo commented

@bogorad commented on GitHub (Dec 13, 2025):

I want it to copy text, not to quit the cli.

ctrl+shft+c? pretty sure it works everywhere.

@bogorad commented on GitHub (Dec 13, 2025): > I want it to copy text, not to quit the cli. `ctrl+shft+c`? pretty sure it works everywhere.

yindo commented

@pschiel commented on GitHub (Dec 22, 2025):

Although my main workstations are Linux and MacOS - I am trying hard to get a flawless experience under Windows too.

A few observations, problems and solutions I have so far:

Environment choices:

Using cmd.exe, powershell.exe or pwsh.exe: All of these lack a bash. While a lot of things also work without bash, it's just worse. Models will often produce bash output, which is also OS independent.
Using WSL: opencode hangs often shortly. WSL in general doesn't work well outside it's internal file system. Very convenient to install, but it performs bad. Lag writes sometimes cause additional "file has been modified".
Using git bash: works better, but extending the git bash is not easy. It lacks pacman, a cc toolchain, installing the small unix goodies is inconvenient (via winget or similar). git bash is kind of a minimal MSYS2.
Using MSYS2 (UCRT64): works best so far. It gives you what git bash does, and with pacman on top, easy install of additional tools.
Using Windows native NodeJS install winget install OpenJS.NodeJS (over MSYS2 NodeJS): otherwise weird issues come up with terminal and more.

Major problem on all MSYS2 based solutions:

Inevitably, paths like /c/some/path will come up. Either by model output, or via some git command (opencode uses git rev-parse to get some things). These paths get wrongly resolved by opencode tools / NodeJS.
Similar, accessing different drives lead to same issues, often paired with relative path traversals including ..\...
Result: file based tool calls will often fail with ENOENT, or write to wrong locations (e.g. writing to C:/e/something instead of E:/something). Even worse: agents will often then switch to sed based editing, which causes even more problems and more awkward behaviour.

Workaround / Solution:

Adding a path normalization, which will (only on win32) convert paths like /c/some/path, /cygdrive/c/some/path, or /mnt/c/some/path to C:/some/path before tool invocation. This results in correct path resolutions in all cases I encountered so far. Will test it a bit more and open a PR later.

@pschiel commented on GitHub (Dec 22, 2025): Although my main workstations are Linux and MacOS - I am trying hard to get a flawless experience under Windows too. A few observations, problems and solutions I have so far: **Environment choices**: - Using `cmd.exe`, `powershell.exe` or `pwsh.exe`: All of these lack a bash. While a lot of things also work without bash, it's just worse. Models will often produce bash output, which is also OS independent. - Using `WSL`: opencode hangs often shortly. WSL in general doesn't work well outside it's internal file system. Very convenient to install, but it performs bad. Lag writes sometimes cause additional "file has been modified". - Using `git bash`: works better, but extending the git bash is not easy. It lacks pacman, a cc toolchain, installing the small unix goodies is inconvenient (via winget or similar). git bash is kind of a minimal MSYS2. - Using `MSYS2` (UCRT64): works **best** so far. It gives you what git bash does, and with pacman on top, easy install of additional tools. - Using Windows native NodeJS install `winget install OpenJS.NodeJS` (over MSYS2 NodeJS): otherwise weird issues come up with terminal and more. **Major problem on all MSYS2 based solutions**: - Inevitably, paths like `/c/some/path` will come up. Either by model output, or via some git command (opencode uses git rev-parse to get some things). These paths get wrongly resolved by opencode tools / NodeJS. - Similar, accessing different drives lead to same issues, often paired with relative path traversals including `..\..`. - Result: file based tool calls will often fail with `ENOENT`, or write to wrong locations (e.g. writing to `C:/e/something` instead of `E:/something`). Even worse: agents will often then switch to `sed` based editing, which causes even more problems and more awkward behaviour. **Workaround / Solution**: Adding a path normalization, which will (only on win32) convert paths like `/c/some/path`, `/cygdrive/c/some/path`, or `/mnt/c/some/path` to `C:/some/path` before tool invocation. This results in correct path resolutions in all cases I encountered so far. Will test it a bit more and open a PR later.

yindo commented

@nielpattin commented on GitHub (Dec 23, 2025):

@pschiel I have a path normalization pr PR#6082 that trying to fix those, maybe you want to look if those match your need. 👀

@nielpattin commented on GitHub (Dec 23, 2025): @pschiel I have a path normalization pr [PR#6082](https://github.com/sst/opencode/pull/6082) that trying to fix those, maybe you want to look if those match your need. 👀

yindo commented

@2315137135 commented on GitHub (Dec 24, 2025):

Sometimes quitting OpenCode will cause any mouse movement/scrolls to print symbols to the console and I'm forced to close that Powershell instance.
I'm enjoying it.

Several of us use Opencode with Git Bash or PowerShell, and this happens to us frequently.

I am NOT enjoying it 😆

I am experiencing the same issue on Windows 10 (pwsh) with OpenCode v1.0.193. It seems to be specific to Windows 10, as I haven't encountered this on Windows 11.

Key Observations:

Trigger: The issue occurs specifically when exiting via Ctrl+C.
Symptoms: If the process terminates immediately after Ctrl+C, moving the mouse starts printing escape sequences to the console.
Inconsistent Behavior: Occasionally, the first Ctrl+C causes the app to hang, and a second Ctrl+C is required to fully exit. Interestingly, in this specific "double Ctrl+C" scenario, the terminal remains clean.
Internal Exit: Using OpenCode’s built-in exit command works perfectly and never triggers the issue.

Potential Cause:
It seems that Ctrl+C might be triggering a forced exit that prevents OpenCode from properly performing terminal cleanup (specifically disabling Mouse Tracking). As a result, the terminal remains in a state where it continues to interpret mouse movements as input characters.

@2315137135 commented on GitHub (Dec 24, 2025): > > Sometimes quitting OpenCode will cause any mouse movement/scrolls to print symbols to the console and I'm forced to close that Powershell instance. > > I'm enjoying it. > > Several of us use Opencode with Git Bash or PowerShell, and this happens to us frequently. > > I am NOT enjoying it 😆 > > <img alt="Image" width="822" height="390.359375" src="https://private-user-images.githubusercontent.com/16762369/523834787-ef9aab63-cf54-4f1e-afbd-7030c0ce1d4d.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjY1NTgwOTgsIm5iZiI6MTc2NjU1Nzc5OCwicGF0aCI6Ii8xNjc2MjM2OS81MjM4MzQ3ODctZWY5YWFiNjMtY2Y1NC00ZjFlLWFmYmQtNzAzMGMwY2UxZDRkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTEyMjQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUxMjI0VDA2Mjk1OFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTMxMzJiOTBhNmNiN2FjNzdlZGY0NmNlZGVkMDAyNTU5YjRkMDE3MTk0OGZhODZmNzQ0YjE5OWJjOWY5NTNhMmYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.A9YLajIKIywKiiHQ0BiiGct_hvRzuSrYv2g-ToKuytA"> I am experiencing the same issue on **Windows 10** (pwsh) with OpenCode **v1.0.193**. It seems to be specific to Windows 10, as I haven't encountered this on Windows 11. **Key Observations:** - **Trigger**: The issue occurs specifically when exiting via `Ctrl+C`. - **Symptoms**: If the process terminates immediately after `Ctrl+C`, moving the mouse starts printing escape sequences to the console. - **Inconsistent Behavior**: Occasionally, the first `Ctrl+C` causes the app to hang, and a second `Ctrl+C` is required to fully exit. Interestingly, in this specific "double Ctrl+C" scenario, the terminal remains clean. - **Internal Exit**: Using OpenCode’s built-in exit command works perfectly and never triggers the issue. **Potential Cause:** It seems that `Ctrl+C` might be triggering a forced exit that prevents OpenCode from properly performing terminal cleanup (specifically disabling **Mouse Tracking**). As a result, the terminal remains in a state where it continues to interpret mouse movements as input characters.

yindo commented

@JosXa commented on GitHub (Dec 24, 2025):

I exported SHELL=nu and been living happily so far, after telling opencode we're running nushell for everything. Best of both worlds, especially since I switch between NixOS and Windows a lot.

@JosXa commented on GitHub (Dec 24, 2025): I exported SHELL=nu and been living happily so far, after telling opencode we're running nushell for everything. Best of both worlds, especially since I switch between NixOS and Windows a lot.

yindo commented

@rekram1-node commented on GitHub (Dec 24, 2025):

I believe there is a bun bug that causes that corruption on ctrl+c, we are working on it

@rekram1-node commented on GitHub (Dec 24, 2025): I believe there is a bun bug that causes that corruption on ctrl+c, we are working on it

yindo commented

@nielpattin commented on GitHub (Dec 24, 2025):

I exported SHELL=nu and been living happily so far, after telling opencode we're running nushell for everything. Best of both worlds, especially since I switch between NixOS and Windows a lot.

Do you feed it docs of nu, or just let it run by itself? Some llm might not able to up to date with the nu command. I often got error or wrong command, and it has to try at least 1-2 fixes until it able to solve the problem… So I just Git Bash…

@nielpattin commented on GitHub (Dec 24, 2025): > I exported SHELL=nu and been living happily so far, after telling opencode we're running nushell for everything. Best of both worlds, especially since I switch between NixOS and Windows a lot. Do you feed it docs of nu, or just let it run by itself? Some llm might not able to up to date with the nu command. I often got error or wrong command, and it has to try at least 1-2 fixes until it able to solve the problem… So I just Git Bash…

yindo commented

@JosXa commented on GitHub (Dec 25, 2025):

I exported SHELL=nu and been living happily so far, after telling opencode we're running nushell for everything. Best of both worlds, especially since I switch between NixOS and Windows a lot.

Do you feed it docs of nu, or just let it run by itself? Some llm might not able to up to date with the nu command. I often got error or wrong command, and it has to try at least 1-2 fixes until it able to solve the problem… So I just Git Bash…

Usually it gets it wrong once but then automatically understands how to run things from there on... but I use Claude models a lot right now

@JosXa commented on GitHub (Dec 25, 2025): > > I exported SHELL=nu and been living happily so far, after telling opencode we're running nushell for everything. Best of both worlds, especially since I switch between NixOS and Windows a lot. > > Do you feed it docs of nu, or just let it run by itself? Some llm might not able to up to date with the nu command. I often got error or wrong command, and it has to try at least 1-2 fixes until it able to solve the problem… So I just Git Bash… Usually it gets it wrong once but then automatically understands how to run things from there on... but I use Claude models a lot right now

yindo commented

@machinekoder commented on GitHub (Jan 8, 2026):

I've been using the Windows Desktop binary for a few days and it works great. One thing I would suggest is to rename the opencode-cli binary to opencode and the gui binary to opencode-gui for example, plus an option in the installer to add the install path to the system environment so one can quickly use opencodes TUI or CLI with the original opencode binary name as well. This also would enable the VSCode extension to work with the same install without any modifications.

Moreover I have noticed that ripgrep doesn't work out of the box on Windows. Maybe an alternative could be used or ripgrep could be installed during the installer process as well (when not already there). Alternatively some message in the GUI/TUI that it can be installed easily (e.g. with winget).

@machinekoder commented on GitHub (Jan 8, 2026): I've been using the Windows Desktop binary for a few days and it works great. One thing I would suggest is to rename the opencode-cli binary to opencode and the gui binary to opencode-gui for example, plus an option in the installer to add the install path to the system environment so one can quickly use opencodes TUI or CLI with the original opencode binary name as well. This also would enable the VSCode extension to work with the same install without any modifications. Moreover I have noticed that ripgrep doesn't work out of the box on Windows. Maybe an alternative could be used or ripgrep could be installed during the installer process as well (when not already there). Alternatively some message in the GUI/TUI that it can be installed easily (e.g. with winget).

yindo commented

https://github.com/NSPC911/le-bucket/blob/master/bucket%2Fopencode-desktop.json

@NSPC911 commented on GitHub (Jan 8, 2026):

I've been using the Windows Desktop binary for a few days and it works great. One thing I would suggest is to rename the opencode-cli binary to opencode and the gui binary to opencode-gui for example, plus an option in the installer to add the install path to the system environment so one can quickly use opencodes TUI or CLI with the original opencode binary name as well. This also would enable the VSCode extension to work with the same install without any modifications.

had to pull off some funny scoop magic to get it working, first time using a 7zip script

basically this manifest installs opencode cli as opencode, and the gui as a start menu shortcut

@NSPC911 commented on GitHub (Jan 8, 2026): > I've been using the Windows Desktop binary for a few days and it works great. One thing I would suggest is to rename the opencode-cli binary to opencode and the gui binary to opencode-gui for example, plus an option in the installer to add the install path to the system environment so one can quickly use opencodes TUI or CLI with the original opencode binary name as well. This also would enable the VSCode extension to work with the same install without any modifications. had to pull off some funny scoop magic to get it working, first time using a 7zip script https://github.com/NSPC911/le-bucket/blob/master/bucket%2Fopencode-desktop.json basically this manifest installs opencode cli as opencode, and the gui as a start menu shortcut

yindo commented

@machinekoder commented on GitHub (Jan 10, 2026):

@NSPC911 awesome, eventually it would be great to have winget support

@machinekoder commented on GitHub (Jan 10, 2026): @NSPC911 awesome, eventually it would be great to have winget support

yindo commented

@JosXa commented on GitHub (Jan 10, 2026):

Can we finally get copy pasting Win+Shift+S snipped images into the session? All workarounds suck and take so much time

@JosXa commented on GitHub (Jan 10, 2026): Can we finally get copy pasting Win+Shift+S snipped images into the session? All workarounds suck and take so much time

yindo commented

@NSPC911 commented on GitHub (Jan 10, 2026):

Can we finally get copy pasting Win+Shift+S snipped images into the session? All workarounds suck and take so much time

It's Ctrl+Shift+V to paste from clipboard iirc

@NSPC911 commented on GitHub (Jan 10, 2026): > Can we finally get copy pasting Win+Shift+S snipped images into the session? All workarounds suck and take so much time It's Ctrl+Shift+V to paste from clipboard iirc

yindo commented

@Hona commented on GitHub (Jan 10, 2026):

Can we finally get copy pasting Win+Shift+S snipped images into the session? All workarounds suck and take so much time

If you disable trim on paste setting inside windows terminal then you can paste from clipboard

@Hona commented on GitHub (Jan 10, 2026): > Can we finally get copy pasting Win+Shift+S snipped images into the session? All workarounds suck and take so much time If you disable trim on paste setting inside windows terminal then you can paste from clipboard

yindo commented

@bogorad commented on GitHub (Jan 11, 2026):

I got so tired of constant issues (bash, wrong tools, etc), came up with this wrapper. This runs the server as a pwsh subprocess, runs git-bash in it with opencode as argument. Also sets the envvar.

Doc inside.

@bogorad commented on GitHub (Jan 11, 2026): I got so tired of constant issues (bash, wrong tools, etc), came up with [this wrapper](https://gist.github.com/bogorad/66604d2c521126e337e8433ba374d528). This runs the server as a pwsh subprocess, runs git-bash in it with opencode as argument. Also sets the envvar. Doc inside.

yindo commented

@pschiel commented on GitHub (Jan 11, 2026):

I got so tired of constant issues (bash, wrong tools, etc), came up with this wrapper. This runs the server as a pwsh subprocess, runs git-bash in it with opencode as argument. Also sets the envvar.

Doc inside.

issues remain the same. only stable solution I had so far is rewriting/normalizing paths to forward slashes, which is supported in all the shells (pwsh, bash, cmd). backslashes cause inherent problems, and they will inevitably come up when working with windows.

with that approach, zero problems anymore with any tools, LSP and permission checks.

@pschiel commented on GitHub (Jan 11, 2026): > I got so tired of constant issues (bash, wrong tools, etc), came up with [this wrapper](https://gist.github.com/bogorad/66604d2c521126e337e8433ba374d528). This runs the server as a pwsh subprocess, runs git-bash in it with opencode as argument. Also sets the envvar. > > Doc inside. issues remain the same. only stable solution I had so far is rewriting/normalizing paths to forward slashes, which is supported in all the shells (pwsh, bash, cmd). backslashes cause inherent problems, and they will inevitably come up when working with windows. with that approach, zero problems anymore with any tools, LSP and permission checks.

yindo commented

@bogorad commented on GitHub (Jan 11, 2026):

only stable solution I had so far is rewriting/normalizing paths to forward slashes

I don't follow. do you do it via some sort of hooks prior to executing each command?

@bogorad commented on GitHub (Jan 11, 2026): > only stable solution I had so far is rewriting/normalizing paths to forward slashes I don't follow. do you do it via some sort of hooks prior to executing each command?

yindo commented

@pschiel commented on GitHub (Jan 11, 2026):

only stable solution I had so far is rewriting/normalizing paths to forward slashes

I don't follow. do you do it via some sort of hooks prior to executing each command?

no, it's done by using and extending the existing Filesystem class, along with a flag to toggle it if someone doesn't want it
https://github.com/anomalyco/opencode/pull/6763/files

with this, the tool unit tests also pass (several fail currently on Windows)

@pschiel commented on GitHub (Jan 11, 2026): > > only stable solution I had so far is rewriting/normalizing paths to forward slashes > > I don't follow. do you do it via some sort of hooks prior to executing each command? no, it's done by using and extending the existing `Filesystem` class, along with a flag to toggle it if someone doesn't want it https://github.com/anomalyco/opencode/pull/6763/files with this, the tool unit tests also pass (several fail currently on Windows)

yindo commented

@JosXa commented on GitHub (Jan 12, 2026):

@Hona @NSPC911 re screenshots:
Please show me how, I have heard from multiple people that they have made it work, but it just doesn't for me...

Spamming Ctrl+Shift+V, Ctrl+V, etc. here after snipping:
https://github.com/user-attachments/assets/73502faa-11da-4928-ba59-8d8e00eb0fa6

But pasting full paths works:
https://github.com/user-attachments/assets/976f5db4-d77d-4bb9-acf2-f7af56f5c832

Okay, so I guess I'll just use ShareX with a "copy file path after snippng" setting, that works for me

@JosXa commented on GitHub (Jan 12, 2026): @Hona @NSPC911 re screenshots: Please show me how, I have heard from multiple people that they have made it work, but it just doesn't for me... <img width="629" height="56" alt="Image" src="https://github.com/user-attachments/assets/ffc3318a-221c-4cb3-af95-1fdff1d07922" /> Spamming Ctrl+Shift+V, Ctrl+V, etc. here after snipping: https://github.com/user-attachments/assets/73502faa-11da-4928-ba59-8d8e00eb0fa6 But pasting full paths works: https://github.com/user-attachments/assets/976f5db4-d77d-4bb9-acf2-f7af56f5c832 Okay, so I guess I'll just use ShareX with a "copy file path after snippng" setting, that works for me

yindo commented

@bramburn commented on GitHub (Jan 12, 2026):

Maybe best to give up

Regards,

B.Ramburn BSc (Hons) LLM MCIArb
Snr. Quantity Surveyor & Director at Icelabz

On Mon, 12 Jan 2026, 16:58 Joscha Götzer, @.***> wrote:

JosXa left a comment (anomalyco/opencode#631)
https://github.com/anomalyco/opencode/issues/631#issuecomment-3739545860

@Hona https://github.com/Hona @NSPC911 https://github.com/NSPC911 re
screenshots:
Please show me how, I have heard from multiple people that they have made
it work, but it just doesn't for me...
image.png (view on web)
https://github.com/user-attachments/assets/ffc3318a-221c-4cb3-af95-1fdff1d07922

Spamming Ctrl+Shift+V, Ctrl+V, etc. here after snipping:

https://github.com/user-attachments/assets/73502faa-11da-4928-ba59-8d8e00eb0fa6

But pasting full paths works:

https://github.com/user-attachments/assets/976f5db4-d77d-4bb9-acf2-f7af56f5c832

—
Reply to this email directly, view it on GitHub
https://github.com/anomalyco/opencode/issues/631#issuecomment-3739545860,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUTT3PHGTPWJAUYXRWV5H34GPHFBAVCNFSM6AAAAACAVSP5UGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZZGU2DKOBWGA
.
You are receiving this because you commented.Message ID:
@.***>

@bramburn commented on GitHub (Jan 12, 2026): Maybe best to give up Regards, B.Ramburn BSc (Hons) LLM MCIArb Snr. Quantity Surveyor & Director at Icelabz On Mon, 12 Jan 2026, 16:58 Joscha Götzer, ***@***.***> wrote: > *JosXa* left a comment (anomalyco/opencode#631) > <https://github.com/anomalyco/opencode/issues/631#issuecomment-3739545860> > > @Hona <https://github.com/Hona> @NSPC911 <https://github.com/NSPC911> re > screenshots: > Please show me how, I have heard from multiple people that they have made > it work, but it just doesn't for me... > image.png (view on web) > <https://github.com/user-attachments/assets/ffc3318a-221c-4cb3-af95-1fdff1d07922> > > Spamming Ctrl+Shift+V, Ctrl+V, etc. here after snipping: > > https://github.com/user-attachments/assets/73502faa-11da-4928-ba59-8d8e00eb0fa6 > > But pasting full paths works: > > https://github.com/user-attachments/assets/976f5db4-d77d-4bb9-acf2-f7af56f5c832 > > — > Reply to this email directly, view it on GitHub > <https://github.com/anomalyco/opencode/issues/631#issuecomment-3739545860>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACUTT3PHGTPWJAUYXRWV5H34GPHFBAVCNFSM6AAAAACAVSP5UGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZZGU2DKOBWGA> > . > You are receiving this because you commented.Message ID: > ***@***.***> >

yindo commented

@pschiel commented on GitHub (Jan 12, 2026):

Spamming Ctrl+Shift+V, Ctrl+V, etc. here after snipping: https://github.com/user-attachments/assets/73502faa-11da-4928-ba59-8d8e00eb0fa6

what tool are you using? it works with standard Windows "Snipping Tool", or when you open a picture with default Photo Viewer and press ctrl+c

@pschiel commented on GitHub (Jan 12, 2026): > Spamming Ctrl+Shift+V, Ctrl+V, etc. here after snipping: https://github.com/user-attachments/assets/73502faa-11da-4928-ba59-8d8e00eb0fa6 what tool are you using? it works with standard Windows "Snipping Tool", or when you open a picture with default Photo Viewer and press ctrl+c

yindo commented

@jdwilsonjr commented on GitHub (Jan 12, 2026):

Maybe best to give up

B.Ramburn BSc (Hons) LLM MCIArb

sadly, have to agree. gave up running Opencode under Windows a long time ago.

@jdwilsonjr commented on GitHub (Jan 12, 2026): > Maybe best to give up > > B.Ramburn BSc (Hons) LLM MCIArb sadly, have to agree. gave up running Opencode under Windows a long time ago.

yindo commented

@duaneking commented on GitHub (Jan 15, 2026):

It honestly feels like open code is not as open as it claims to be simply because it seems to be diminishing and minimizing access to BYOM; On Windows you can't even figure out where your config file is without having to google it because the docs are so unclear.

@duaneking commented on GitHub (Jan 15, 2026): It honestly feels like open code is not as open as it claims to be simply because it seems to be diminishing and minimizing access to BYOM; On Windows you can't even figure out where your config file is without having to google it because the docs are so unclear.

yindo commented

https://opencode.ai/docs/providers
https://opencode.ai/docs/config/

@2315137135 commented on GitHub (Jan 15, 2026):

It honestly feels like open code is not as open as it claims to be simply because it seems to be diminishing and minimizing access to BYOM; On Windows you can't even figure out where your config file is without having to google it because the docs are so unclear.

Actually, the very first item in the documentation tells you where the config file is, and the second one shows you how to use BYOM.

@2315137135 commented on GitHub (Jan 15, 2026): > It honestly feels like open code is not as open as it claims to be simply because it seems to be diminishing and minimizing access to BYOM; On Windows you can't even figure out where your config file is without having to google it because the docs are so unclear. https://opencode.ai/docs/providers https://opencode.ai/docs/config/ Actually, the very first item in the documentation tells you where the config file is, and the second one shows you how to use BYOM.

yindo commented

@bogorad commented on GitHub (Jan 15, 2026):

On Windows you can't even figure out where your config file is

first thing I do is put this in $PROFILE:

$ENV:HOME = "c:/Users/$env:USERNAME"
$ENV:XDG_CONFIG_HOME = "$ENV:HOME/.config"
$ENV:XDG_DATA_HOME = "$ENV:HOME/.local/share"
$ENV:XDG_CACHE_HOME = "$ENV:HOME/.cache"
$ENV:DOTFILES = "$ENV:HOME/.dotfiles"
$DOTFILES = $ENV:DOTFILES

@bogorad commented on GitHub (Jan 15, 2026): > On Windows you can't even figure out where your config file is first thing I do is put this in $PROFILE: ``` $ENV:HOME = "c:/Users/$env:USERNAME" $ENV:XDG_CONFIG_HOME = "$ENV:HOME/.config" $ENV:XDG_DATA_HOME = "$ENV:HOME/.local/share" $ENV:XDG_CACHE_HOME = "$ENV:HOME/.cache" $ENV:DOTFILES = "$ENV:HOME/.dotfiles" $DOTFILES = $ENV:DOTFILES ```

yindo commented

@bramburn commented on GitHub (Jan 15, 2026):

Give up

Regards,

B.Ramburn BSc (Hons) LLM MCIArb
Snr. Quantity Surveyor & Director at Icelabz

On Thu, 15 Jan 2026, 19:47 Eugene bogorad, @.***> wrote:

bogorad left a comment (anomalyco/opencode#631)
https://github.com/anomalyco/opencode/issues/631#issuecomment-3756578780

On Windows you can't even figure out where your config file is

first thing I do is put this in $PROFILE:

$ENV:HOME = "c:/Users/$env:USERNAME"
$ENV:XDG_CONFIG_HOME = "$ENV:HOME/.config"
$ENV:XDG_DATA_HOME = "$ENV:HOME/.local/share"
$ENV:XDG_CACHE_HOME = "$ENV:HOME/.cache"
$ENV:DOTFILES = "$ENV:HOME/.dotfiles"
$DOTFILES = $ENV:DOTFILES

—
Reply to this email directly, view it on GitHub
https://github.com/anomalyco/opencode/issues/631#issuecomment-3756578780,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUTT3PPG6RKXRYNVK7GDA34G7VEZAVCNFSM6AAAAACAVSP5UGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONJWGU3TQNZYGA
.
You are receiving this because you commented.Message ID:
@.***>

@bramburn commented on GitHub (Jan 15, 2026): Give up Regards, B.Ramburn BSc (Hons) LLM MCIArb Snr. Quantity Surveyor & Director at Icelabz On Thu, 15 Jan 2026, 19:47 Eugene bogorad, ***@***.***> wrote: > *bogorad* left a comment (anomalyco/opencode#631) > <https://github.com/anomalyco/opencode/issues/631#issuecomment-3756578780> > > On Windows you can't even figure out where your config file is > > first thing I do is put this in $PROFILE: > > $ENV:HOME = "c:/Users/$env:USERNAME" > $ENV:XDG_CONFIG_HOME = "$ENV:HOME/.config" > $ENV:XDG_DATA_HOME = "$ENV:HOME/.local/share" > $ENV:XDG_CACHE_HOME = "$ENV:HOME/.cache" > $ENV:DOTFILES = "$ENV:HOME/.dotfiles" > $DOTFILES = $ENV:DOTFILES > > — > Reply to this email directly, view it on GitHub > <https://github.com/anomalyco/opencode/issues/631#issuecomment-3756578780>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACUTT3PPG6RKXRYNVK7GDA34G7VEZAVCNFSM6AAAAACAVSP5UGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONJWGU3TQNZYGA> > . > You are receiving this because you commented.Message ID: > ***@***.***> >

yindo commented

@rekram1-node commented on GitHub (Jan 15, 2026):

@duaneking please explain what isn't clear for you?

@rekram1-node commented on GitHub (Jan 15, 2026): @duaneking please explain what isn't clear for you?

yindo commented

@NSPC911 commented on GitHub (Jan 15, 2026):

It honestly feels like open code is not as open as it claims to be simply because it seems to be diminishing and minimizing access to BYOM; On Windows you can't even figure out where your config file is without having to google it because the docs are so unclear.

It is more common sense than not. There are only three places that config files can traditionally be. It should be in ~/AppData/Local/<app>, ~/AppData/Roaming/<app> (rare) or ~/.config/<app>. If you spared more than 10 seconds, you would have found opencode's config in ~/.config/opencode.

Furthermore, as pointed out by @2315137135, the config path is clearly mentioned in the config.

@NSPC911 commented on GitHub (Jan 15, 2026): > It honestly feels like open code is not as open as it claims to be simply because it seems to be diminishing and minimizing access to BYOM; On Windows you can't even figure out where your config file is without having to google it because the docs are so unclear. It is more common sense than not. There are only three places that config files can traditionally be. It should be in `~/AppData/Local/<app>`, `~/AppData/Roaming/<app>` (rare) or `~/.config/<app>`. If you spared more than 10 seconds, you would have found opencode's config in `~/.config/opencode`. Furthermore, as pointed out by @2315137135, the config path is clearly mentioned in the config.

yindo commented

@Hona commented on GitHub (Jan 15, 2026):

I think we can improve on the discoverability of config locations.
It is not following the traditional Windows paths and using Linux conventions (XDG) with ~ substition for e.g C:\Users\you\ then .config/opencode or .local/share/opencode etc
However all of this is open, and if you use opencode on the opencode repo with these questions its very quick to find

@Hona commented on GitHub (Jan 15, 2026): I think we can improve on the discoverability of config locations. It is not following the traditional Windows paths and using Linux conventions (XDG) with ~ substition for e.g C:\Users\you\ then .config/opencode or .local/share/opencode etc However all of this is open, and if you use opencode on the opencode repo with these questions its very quick to find

yindo commented

@duaneking commented on GitHub (Jan 17, 2026):

@duaneking please explain what isn't clear for you?

All the docs are written for sighted users on Mac and don't consider visually disabled users using screen readers on windows.

And my screen reader (yea, I'm legally blind and am a developer) has problems with the docs I can find, so it kind of feels like maybe I'm not getting access to everything. It's entirely possible that it's there and I just can't see it all, but that would still be a bug for me.

Either way, it would be really nice to see documentation around BYOM, it really feels like for example ollama local network setups feel like they're not supported because the menu system wants you to use a paid service and won't even list ollama that isn't posted in the cloud in a way that they can profit from; the menu I got access to basically makes it look like the only thing thats supported is paid zen services.

I was looking for ways to set up BYOM locally using the ollama stuff I already have working using the Network API as an architectural boundary because my home lab has dedicated hardware running AI stuff for inference, but that's used by multiple local agents and other systems on my home network.

I've had some really good success with using agents to translate sighted stuff to accessible text for me and I want to keep getting more access because it feels like I'm getting back access to a world that was taken from me when they took my eyesight.

@duaneking commented on GitHub (Jan 17, 2026): > @duaneking please explain what isn't clear for you? All the docs are written for sighted users on Mac and don't consider visually disabled users using screen readers on windows. And my screen reader (yea, I'm legally blind and am a developer) has problems with the docs I can find, so it kind of feels like maybe I'm not getting access to everything. It's entirely possible that it's there and I just can't see it all, but that would still be a bug for me. Either way, it would be really nice to see documentation around BYOM, it really feels like for example ollama local network setups feel like they're not supported because the menu system wants you to use a paid service and won't even list ollama that isn't posted in the cloud in a way that they can profit from; the menu I got access to basically makes it look like the only thing thats supported is paid zen services. I was looking for ways to set up BYOM locally using the ollama stuff I already have working using the Network API as an architectural boundary because my home lab has dedicated hardware running AI stuff for inference, but that's used by multiple local agents and other systems on my home network. I've had some really good success with using agents to translate sighted stuff to accessible text for me and I want to keep getting more access because it feels like I'm getting back access to a world that was taken from me when they took my eyesight.

yindo commented

@pschiel commented on GitHub (Jan 17, 2026):

All the docs are written for sighted users on Mac and don't consider visually disabled users using screen readers on windows.

here's a tip:

clone the opencode repo from https://github.com/anomalyco/opencode
start opencode in that directory, and tell it: "docs are in packages/web/src/content/docs"

it will then be able to answer your questions e.g. how to setup ollama.

@pschiel commented on GitHub (Jan 17, 2026): > All the docs are written for sighted users on Mac and don't consider visually disabled users using screen readers on windows. here's a tip: - clone the opencode repo from https://github.com/anomalyco/opencode - start opencode in that directory, and tell it: "docs are in packages/web/src/content/docs" it will then be able to answer your questions e.g. how to setup ollama.

yindo commented

@Stevie-okay commented on GitHub (Jan 18, 2026):

Hope this is the right place can't find anything about it.
Running the .exe and GUI.

How do you delete sessions?

There is a archive button and a close button next to the project folder.
But if you add the same project folder again it reopens the old closed session.

Or what files need to be deleted to remove a session, its history and start with a fresh plate?
Mainly asking due to the latest bug causing a history swap from one session to another.

EDIT:
Think i found the files for a reset. Fairly difficult since on windows it creates folders all over the place like a mycelium.

C:\Users\user.local\share\opencode\storage\session -> Delete all content
C:\Users\user.local\share\opencode\storage\session_diff -> Delete all content
C:\Users\user.local\share\opencode\storage\messages -> Delete all content
C:\Users\user.local\share\opencode\storage\part -> Delete all content

C:\Users\user\AppData\Roaming\ai.opencode.desktop -> workspace -> Deleted
C:\Users\user\AppData\Roaming\ai.opencode.desktop -> opencode.global.dat -> {}

@Stevie-okay commented on GitHub (Jan 18, 2026): Hope this is the right place can't find anything about it. Running the .exe and GUI. **How do you delete sessions**? There is a archive button and a close button next to the project folder. But if you add the same project folder again it reopens the old closed session. Or what files need to be deleted to remove a session, its history and start with a fresh plate? Mainly asking due to the latest bug causing a history swap from one session to another. EDIT: Think i found the files for a reset. Fairly difficult since on windows it creates folders all over the place like a mycelium. > C:\Users\user\.local\share\opencode\storage\session -> Delete all content > C:\Users\user\.local\share\opencode\storage\session_diff -> Delete all content > C:\Users\user\.local\share\opencode\storage\messages -> Delete all content > C:\Users\user\.local\share\opencode\storage\part -> Delete all content > > C:\Users\user\AppData\Roaming\ai.opencode.desktop -> workspace -> Deleted > C:\Users\user\AppData\Roaming\ai.opencode.desktop -> opencode.global.dat -> {}

yindo commented

@JosXa commented on GitHub (Jan 18, 2026):

How do you delete sessions?

In the TUI:

On Desktop: No clue.

@JosXa commented on GitHub (Jan 18, 2026): > **How do you delete sessions**? In the TUI: <img width="715" height="297" alt="Image" src="https://github.com/user-attachments/assets/4a8de4a8-d954-46b5-b5cc-241272b1d6cf" /> On Desktop: No clue.

yindo commented

@edision commented on GitHub (Jan 19, 2026):

opencode 1.1.25
bun1.3.6
Switching the nodejs version back to 22.x will prevent it from crashing. It should be that bun encountered incompatible functions when running the node script.

@edision commented on GitHub (Jan 19, 2026): opencode 1.1.25 bun1.3.6 Switching the nodejs version back to 22.x will prevent it from crashing. It should be that bun encountered incompatible functions when running the node script.

yindo commented

@1103394945 commented on GitHub (Jan 23, 2026):

When I use the Nvidia API, the conversation returns a 404.> our windows support isn't really there - creating this one super issue to track all problems

@1103394945 commented on GitHub (Jan 23, 2026): When I use the Nvidia API, the conversation returns a 404.> our windows support isn't really there - creating this one super issue to track all problems

yindo commented

@1103394945 commented on GitHub (Jan 23, 2026):

When I use the Nvidia API, the conversation returns a 404.> our windows support isn't really there - creating this one super issue to track all problems

@1103394945 commented on GitHub (Jan 23, 2026): When I use the Nvidia API, the conversation returns a 404.> our windows support isn't really there - creating this one super issue to track all problems

yindo commented

@1103394945 commented on GitHub (Jan 23, 2026):

When I use the Nvidia API, the conversation returns a 404.

@1103394945 commented on GitHub (Jan 23, 2026): When I use the Nvidia API, the conversation returns a 404.

yindo commented

@756maker commented on GitHub (Jan 25, 2026):

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

@756maker commented on GitHub (Jan 25, 2026): > our windows support isn't really there - creating this one super issue to track all problems

yindo commented

https://github.com/user-attachments/assets/eb0c93b5-7deb-49f4-9b34-6a4243f75fe1

@cjt687724 commented on GitHub (Jan 26, 2026):

On Windows 11, running opencode in the IntelliJ IDEA terminal fails to display correctly.

@cjt687724 commented on GitHub (Jan 26, 2026): On Windows 11, running opencode in the IntelliJ IDEA terminal fails to display correctly. https://github.com/user-attachments/assets/eb0c93b5-7deb-49f4-9b34-6a4243f75fe1

yindo commented

@bramburn commented on GitHub (Jan 26, 2026):

Damn sorry to hear

Regards,

B.Ramburn BSc (Hons) LLM MCIArb
Snr. Quantity Surveyor & Director at Icelabz

On Mon, 26 Jan 2026, 07:33 zhuzn, @.***> wrote:

haimu0427 left a comment (anomalyco/opencode#631)
https://github.com/anomalyco/opencode/issues/631#issuecomment-3798230564

This program sometimes works, sometimes it doesn't start properly, the
terminal message is as follows, I have tried uninstalling and reinstalling
several times but the problem occurs from time to time, and it also doesn't
start properly when I run other bun projects.
image.png (view on web)
https://github.com/user-attachments/assets/32d60aea-3a2a-4188-ad8c-3afc2f5cfaf7

—
Reply to this email directly, view it on GitHub
https://github.com/anomalyco/opencode/issues/631#issuecomment-3798230564,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUTT3I2BXCN6A55VMYU4YD4IW7LZAVCNFSM6AAAAACAVSP5UGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOOJYGIZTANJWGQ
.
You are receiving this because you commented.Message ID:
@.***>

@bramburn commented on GitHub (Jan 26, 2026): Damn sorry to hear Regards, B.Ramburn BSc (Hons) LLM MCIArb Snr. Quantity Surveyor & Director at Icelabz On Mon, 26 Jan 2026, 07:33 zhuzn, ***@***.***> wrote: > *haimu0427* left a comment (anomalyco/opencode#631) > <https://github.com/anomalyco/opencode/issues/631#issuecomment-3798230564> > > This program sometimes works, sometimes it doesn't start properly, the > terminal message is as follows, I have tried uninstalling and reinstalling > several times but the problem occurs from time to time, and it also doesn't > start properly when I run other bun projects. > image.png (view on web) > <https://github.com/user-attachments/assets/32d60aea-3a2a-4188-ad8c-3afc2f5cfaf7> > > — > Reply to this email directly, view it on GitHub > <https://github.com/anomalyco/opencode/issues/631#issuecomment-3798230564>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACUTT3I2BXCN6A55VMYU4YD4IW7LZAVCNFSM6AAAAACAVSP5UGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOOJYGIZTANJWGQ> > . > You are receiving this because you commented.Message ID: > ***@***.***> >

yindo commented

@pschiel commented on GitHub (Jan 28, 2026):

please reconsider https://github.com/anomalyco/opencode/pull/6763

latest bug causes git bash to be completely unusable with OpenCode in Windows, resulting in bun segfaulting, when using bash and cwd parameter

more backslash issues keep popping up every week.

@pschiel commented on GitHub (Jan 28, 2026): please reconsider https://github.com/anomalyco/opencode/pull/6763 latest bug causes git bash to be completely unusable with OpenCode in Windows, resulting in bun segfaulting, when using bash and cwd parameter more backslash issues keep popping up every week.

yindo commented

@Branskugel commented on GitHub (Feb 10, 2026):

also, please consider #8395 I can confirm this issue is currently present in the latest scoop release

@Branskugel commented on GitHub (Feb 10, 2026): also, please consider #8395 I can confirm this issue is currently present in the latest scoop release

yindo commented