[FEATURE]: Add Windows arm64 support

[LayZeeDK]

Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

After installing OpenCode on Windows 11 Business arm64 using WinGet, Chocolatey, or npm install --global opencode-ai, the following error is output but no opencode-windows-arm64 npm package exists or is attached to a GitHub Release.

It seems that your package manager failed to install the right version of the opencode CLI for your platform. You can try manually installing the "opencode-windows-arm64" package

Please add Windows arm64 support 🙇‍♂️

[github-actions]

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

• It seems that your package manager failed to install the right version of the opencode CLI for your platform. You can try manually installing the "opencode-windows-x64" package #3002: Same error pattern for Windows x64 - "It seems that your package manager failed to install the right version of the opencode CLI for your platform"

Both issues report the same underlying problem with missing Windows platform-specific packages, just for different architectures (arm64 vs x64). This suggests a broader Windows platform support issue.

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

[rekram1-node]

Will do

[Volko61]

@rekram1-node You're the goat ! I don't use opencode just because there is no windows arm binaries

[rekram1-node]

I think this may be blocked by the upstream bun issue

Ref:

—target | Operating System | Architecture | Modern | Baseline | Libc
-- | -- | -- | -- | -- | --
bun-linux-x64 | Linux | x64 | ✅ | ✅ | glibc
bun-linux-arm64 | Linux | arm64 | ✅ | N/A | glibc
bun-windows-x64 | Windows | x64 | ✅ | ✅ | -
bun-windows-arm64 | Windows | arm64 | ❌ | ❌ | -
bun-darwin-x64 | macOS | x64 | ✅ | ✅ | -
bun-darwin-arm64 | macOS | arm64 | ✅ | N/A | -
bun-linux-x64-musl | Linux | x64 | ✅ | ✅ | musl
bun-linux-arm64-musl | Linux | arm64 | ✅ | N/A

So it likely wont be a simple fix

[thdxr]

and it's even further upstream, webkit is the first thing to figure out
oven-sh/WebKit#105

[mickythompson]

Anthropic, which now owns Bun, would prefer its Claude Code run natively on Windows arm64 instead of its current workaround (likely using emulation layers).

So here's to Anthropic helping Bun achieve Windows arm64 support, which in turn will help OpenCode achieve Windows arm64 support without requiring emulation layers.

[adsharma]

Any chance that we can install it with a different package manager? Lots of good holiday deals on Snapdragon laptops.

[rekram1-node]

has nothing to do w package managers?

[adsharma]

Right. Bun is a JavaScript runtime. Easy to get confused because of bun install ...

[khairm]

Adding a specific bug report that shows the real-world impact of this issue:

TUI Crash on Snapdragon X Elite (Windows 11 ARM64)

Environment:

• OS: Windows 11 ARM64 (Build 10.0.26200.7462)
• • Processor: Snapdragon X Elite - X1E80100 - Qualcomm Oryon CPU
• • • OpenCode Version: 1.1.3 (via curl installer)
• • • • Binary: opencode-windows-x64.zip running under x64 emulation
        Issue:
        opencode auth login crashes with SIGSEGV (exit code 139) immediately after displaying the provider selection TUI. The crash is intermittent - sometimes works, mostly crashes. Tested across PowerShell, CMD, Windows Terminal, and Git Bash with the same result.

Root Cause:
I understand this is blocked upstream by Bun's lack of Windows ARM64 support (and further upstream by WebKit). The x64 binary running under Windows' emulation layer appears to have TUI rendering issues that cause segfaults.

Workaround Request:
While waiting for native ARM64 support, would it be possible to add a --provider flag for non-interactive auth? For example:

opencode auth login --provider anthropic

This would allow ARM64 users to bypass the TUI entirely and complete authentication even when the interactive menu crashes.

With Snapdragon laptops becoming more common (Surface Pro X, various Snapdragon X Elite devices), this workaround would help bridge the gap until upstream dependencies are resolved.