Skip to content

[FEATURE]: Add Windows arm64 support #4340

Closed
Closed
[FEATURE]: Add Windows arm64 support#4340
Assignees
rekram1-node
Labels
discussionUsed for feature requests, proposals, ideas, etc. Open discussionwindows

Description

@LayZeeDK
LayZeeDK
opened on Nov 14, 2025

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 🙇‍♂️

Activity

  1. LayZeeDK
    added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Nov 14, 2025

  2. github-actions commented on Nov 14, 2025

    @github-actions
    github-actionsBot
    on Nov 14, 2025 – with GitHub Actions
    Contributor

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

    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.

  3. rekram1-node commented on Nov 14, 2025

    @rekram1-node
    rekram1-node
    on Nov 14, 2025
    Contributor

    Will do

  4. rekram1-node
    self-assigned this
    on Nov 14, 2025
  5. rekram1-node
    added
    windows
    on Nov 14, 2025

  6. Volko61 commented on Nov 15, 2025

    @Volko61
    Volko61
    on Nov 15, 2025

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

  7. rekram1-node commented on Nov 15, 2025

    @rekram1-node
    rekram1-node
    on Nov 15, 2025
    Contributor

    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

  8. thdxr commented on Nov 17, 2025

    @thdxr
    thdxr
    on Nov 17, 2025
    Member

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

  9. mickythompson commented on Dec 28, 2025

    @mickythompson
    mickythompson
    on Dec 28, 2025

    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.

  10. adsharma commented on Jan 3, 2026

    @adsharma
    adsharma
    on Jan 3, 2026

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

  11. rekram1-node commented on Jan 3, 2026

    @rekram1-node
    rekram1-node
    on Jan 3, 2026
    Contributor

    has nothing to do w package managers?

  12. adsharma commented on Jan 4, 2026

    @adsharma
    adsharma
    on Jan 4, 2026

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

  13. khairm commented on Jan 7, 2026

    @khairm
    khairm
    on Jan 7, 2026

    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.

  14. ccstr commented on Jan 22, 2026

    @ccstr
    ccstr
    on Jan 22, 2026

    Just adding a data point. I tried to use opencode 1.1.13 on a ARM64 Windows machine, without knowing the support is not available. After running opencode to bring out the TUI, it silently quits with no error. With --log-level DEBUG, the last log it writes is

    INFO  2026-01-22T06:49:14 +0ms service=bun cmd=["C:\\.tools\\.npm-global\\node_modules\\opencode-ai\\node_modules\\opencode-windows-x64\\bin\\opencode.exe","install"]

    I would guess it is trying to run a x64 bineary on arm64. The same version works as expected in a x64 machine.

  15. gxsshallot commented on Jan 23, 2026

    @gxsshallot
    gxsshallot
    on Jan 23, 2026

    wait for support + 1

  16. 17 remaining items

  17. LayZeeDK commented on Mar 13, 2026

    @LayZeeDK
    LayZeeDK
    on Mar 13, 2026
    Author

    Good tip, @wisemanny , thanks!

    My output:

    opencode --log-level DEBUG --print-logs
INFO  2026-03-13T10:34:13 +342ms service=default version=0.0.0-dev-202603120428 args=["--log-level","DEBUG","--print-logs"] opencode
INFO  2026-03-13T10:34:13 +4ms service=default directory=D:\projects\sandbox creating instance
INFO  2026-03-13T10:34:13 +1ms service=project directory=D:\projects\sandbox fromDirectory
INFO  2026-03-13T10:34:13 +1ms service=db path=%USERPROFILE%\.local\share\opencode\opencode-dev.db opening database
INFO  2026-03-13T10:34:13 +31ms service=db count=8 mode=bundled applying migrations
INFO  2026-03-13T10:34:13 +26ms service=config path=%USERPROFILE%\.config\opencode\config.json loading
INFO  2026-03-13T10:34:13 +0ms service=config path=%USERPROFILE%\.config\opencode\opencode.json loading
INFO  2026-03-13T10:34:13 +0ms service=config path=%USERPROFILE%\.config\opencode\opencode.jsonc loading
ERROR 2026-03-13T10:34:13 +6ms service=default e=Failed to initialize OpenTUI render library: bun:ffi dlopen() is not available in this build (TinyCC is disabled) rejection
ERROR 2026-03-13T10:34:13 +0ms service=default Error: Failed to initialize OpenTUI render library: bun:ffi dlopen() is not available in this build (TinyCC is disabled)

  18. LayZeeDK commented on Mar 13, 2026

    @LayZeeDK
    LayZeeDK
    on Mar 13, 2026
    Author

    Yeah, sorry about mentioning the Prism x86_64 emulation, that's unrelated to the dev build. I do run the Windows arm64 build of Node.js and it does stick to arm64 end-to-end when using the dev build from what I can tell.

  19. wisemanny commented on Mar 13, 2026

    @wisemanny
    wisemanny
    on Mar 13, 2026

    With the way Prism works - can't you just run the x64 build on Windows ARM?

    @Hona for me it did not work (though it works for other apps, the Prism working well). At some point like 3 months ago, opencode via Prism started to crash at random points during start process leaving terminal in a weird state in terms of configuration (control codes would print and so on). So, I was waiting for bun to support arm64 and then opencode to support it to run natively. Now I have native node, native bun and seems to be native arm64 opencode, but the TUI did not work and I shared that. It feels like some minor steps are left.

  20. Hona commented on Mar 13, 2026

    @Hona
    Hona
    on Mar 13, 2026
    Member

    Bun doesn't fully support arm64 on windows yet. That's why the TUI doesn't work. FFI is entirely disabled so I created the issue in their repo

  21. machinekoder commented on Mar 18, 2026

    @machinekoder
    machinekoder
    on Mar 18, 2026

    opencode via Prism started to crash at random points during start

    Probably with this update https://techcommunity.microsoft.com/blog/windowsosplatform/windows-on-arm-runs-more-apps-and-games-with-new-prism-update/4475631 Note this can be disabled in the Windows Emulation compatibility settings.

    I have similar problems on ARM64 in Parallels

  22. machinekoder commented on Mar 18, 2026

    @machinekoder
    machinekoder
    on Mar 18, 2026
    Image confirmed, disabling AVX AVX2 Emulation makes it fly again (the x64 binary), this feature was introduced with Windows 11 Build 26100.6899 (check with winver.exe) @wisemanny

  23. wisemanny commented on Mar 18, 2026

    @wisemanny
    wisemanny
    on Mar 18, 2026

    @machinekoder wow, good catch and thanks for sharing!

  24. LayZeeDK commented on Mar 24, 2026

    @LayZeeDK
    LayZeeDK
    on Mar 24, 2026
    Author

    The Change emulation settings for opencode.exe is disabled on my machine.

  25. sondreb commented on Mar 26, 2026

    @sondreb
    sondreb
    on Mar 26, 2026

    The Change emulation settings for opencode.exe is disabled on my machine.

    Same here, been waiting long time for ARM support so happy to see it's installable now, but the TUI doesn't run. Is there any way at all to make it work yet?

    opencode web works on Windows ARM, so that's good enough for now! Thanks for all the hard work on ARM support 👍

  26. Hona commented on Mar 26, 2026

    @Hona
    Hona
    on Mar 26, 2026
    Member

    Yeah we're waiting on bun to patch FFI which is disabled for them.

  27. LayZeeDK commented on Mar 28, 2026

    @LayZeeDK
    LayZeeDK
    on Mar 28, 2026
    Author

    I didn't know about opencode web. Thanks for the pointer, @sondreb!

  28. hmartinez82 commented on Apr 11, 2026

    @hmartinez82
    hmartinez82
    on Apr 11, 2026

    Bun doesn't fully support arm64 on windows yet. That's why the TUI doesn't work. FFI is entirely disabled so I created the issue in their repo

    Can you link the issue here?

  29. LayZeeDK commented on Apr 11, 2026

    @LayZeeDK
    LayZeeDK
    on Apr 11, 2026
    Author

    Bun doesn't fully support arm64 on windows yet. That's why the TUI doesn't work. FFI is entirely disabled so I created the issue in their repo

    Can you link the issue here?

    #4340 (comment)

  30. wisemanny commented on Jul 29, 2026

    @wisemanny
    wisemanny
    on Jul 29, 2026

    I installed "2026-07 Preview Update (KB5101684) (26200.8973)" and cannot longer load the x64 opencode in emulation mode. Checked emulation settings and tried a few previous versions, no luck. It does not even print logs nor creates log files. If anyone finds a way to fix, please share. I was not able. Even Log shows this:

    Faulting application name: opencode.exe, version: 1.3.14.0, time stamp: 0x6a03aae4
    Faulting module name: xtajit64.dll, version: 10.0.26100.8972, time stamp: 0xd680d577
    Exception code: 0xc0000005
    Fault offset: 0x000000000001bdfc
    Faulting process id: 0x6FF8
    Faulting application start time: 0x1DD1F426B10CD1D
    Faulting application path: C:\Users\xxxxxxxx\scoop\persist\bun\install\global\node_modules\opencode-windows-x64\bin\opencode.exe
    Faulting module path: C:\WINDOWS\System32\xtajit64.dll
    Report Id: 2eb11b1d-58cf-4a91-b0ed-9161b62c4e65
    Faulting package full name:
    Faulting package-relative application ID:

  31. LayZeeDK commented on Oct 15, 2026

    @LayZeeDK
    LayZeeDK
    on Oct 15, 2026
    Author

    Definitely working out-of-the-box in OpenCode version 2.0.29. Thanks, team!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

discussionUsed for feature requests, proposals, ideas, etc. Open discussionwindows

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions