anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Windows: opencode-cli crashes with illegal instruction (0xC000001D) on AMD FX-8350 starting in v1.1.52 #8800

New Issue
Open
opened 2026-02-16 18:10:53 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:10:53 -05:00
Owner
Copy Link
Copy Source

Originally created by @mattu08 on GitHub (Feb 7, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

Describe the bug

On Windows, OpenCode Desktop versions 1.1.52 and newer fail to start with:

"Failed to spawn OpenCode Server"

This happens because opencode-cli.exe crashes immediately on launch with an illegal instruction exception.

Versions up to 1.1.51 work correctly on the same machine.

Reproduction steps

  1. Install OpenCode Desktop v1.1.52 or newer on Windows
  2. Launch OpenCode
  3. App fails immediately with “Failed to spawn OpenCode Server”
  4. Running opencode-cli.exe manually also exits instantly with no output

Expected behavior

OpenCode Desktop should start the local server and open normally, as it does in v1.1.51 and earlier.

Actual behavior

The local server never starts. No logs are written by OpenCode.

Windows Event Viewer shows opencode-cli.exe crashing immediately.

Diagnostic details

Last working version

  • ✅ v1.1.51

First broken version

  • ❌ v1.1.52

CPU

  • AMD FX-8350 Eight-Core Processor (Piledriver)

OS

  • Windows 11 (64-bit)

Exception (Event Viewer → Application Error)
Faulting application name: opencode-cli.exe
Exception code: 0xC000001D (Illegal instruction)
Faulting module name: opencode-cli.exe

Additional notes

  • Antivirus fully disabled → no change
  • Clean reinstall and cache removal → no change
  • opencode-cli.exe exits silently even with --help or --version
  • Older versions work consistently on the same system

Suspected cause

It looks like opencode-cli.exe (or a bundled runtime such as Bun) was rebuilt in v1.1.52 with CPU instructions not supported on older AMD CPUs (e.g. FX/Piledriver).

A legacy/compat build or adjusted compiler flags (e.g. targeting baseline x86-64) would likely resolve this.

Impact

Users on older but still common CPUs cannot run OpenCode Desktop beyond v1.1.51 on Windows.

Plugins

None.

OpenCode version

v1.1.52 or newer*

Steps to reproduce

  1. Install OpenCode Desktop v1.1.52 or newer on Windows
  2. Launch OpenCode
  3. App fails immediately with “Failed to spawn OpenCode Server”
  4. Running opencode-cli.exe manually also exits instantly with no output

Screenshot and/or share link

No response

Operating System

Windows 11

Terminal

PowerShell

Originally created by @mattu08 on GitHub (Feb 7, 2026). Originally assigned to: @rekram1-node on GitHub. ### Description ### Describe the bug On Windows, OpenCode Desktop versions **1.1.52 and newer** fail to start with: > "Failed to spawn OpenCode Server" This happens because `opencode-cli.exe` crashes immediately on launch with an **illegal instruction** exception. Versions **up to 1.1.51 work correctly** on the same machine. --- ### Reproduction steps 1. Install OpenCode Desktop **v1.1.52 or newer** on Windows 2. Launch OpenCode 3. App fails immediately with “Failed to spawn OpenCode Server” 4. Running `opencode-cli.exe` manually also exits instantly with no output --- ### Expected behavior OpenCode Desktop should start the local server and open normally, as it does in v1.1.51 and earlier. --- ### Actual behavior The local server never starts. No logs are written by OpenCode. Windows Event Viewer shows `opencode-cli.exe` crashing immediately. --- ### Diagnostic details **Last working version** - ✅ v1.1.51 **First broken version** - ❌ v1.1.52 **CPU** - AMD FX-8350 Eight-Core Processor (Piledriver) **OS** - Windows 11 (64-bit) **Exception (Event Viewer → Application Error)** Faulting application name: opencode-cli.exe Exception code: 0xC000001D (Illegal instruction) Faulting module name: opencode-cli.exe **Additional notes** - Antivirus fully disabled → no change - Clean reinstall and cache removal → no change - opencode-cli.exe exits silently even with `--help` or `--version` - Older versions work consistently on the same system --- ### Suspected cause It looks like `opencode-cli.exe` (or a bundled runtime such as Bun) was rebuilt in v1.1.52 with CPU instructions not supported on older AMD CPUs (e.g. FX/Piledriver). A legacy/compat build or adjusted compiler flags (e.g. targeting baseline x86-64) would likely resolve this. --- ### Impact Users on older but still common CPUs cannot run OpenCode Desktop beyond v1.1.51 on Windows. ### Plugins None. ### OpenCode version v1.1.52 or newer* ### Steps to reproduce 1. Install OpenCode Desktop v1.1.52 or newer on Windows 2. Launch OpenCode 3. App fails immediately with “Failed to spawn OpenCode Server” 4. Running opencode-cli.exe manually also exits instantly with no output ### Screenshot and/or share link _No response_ ### Operating System Windows 11 ### Terminal PowerShell
yindo added the windowsbugweb labels 2026-02-16 18:10:53 -05:00
yindo commented 2026-02-16 18:10:53 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 7, 2026):

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

  • #12553: Windows: Installer should detect CPU capabilities and use baseline binary for CPUs without AVX2 (discusses the same root cause with Intel CPUs lacking AVX2)
  • #12521: Bug: After updating to 1.1.53 from 1.1.51, the desktop app doesn't create OpenCode server and fails to start (same "Failed to spawn OpenCode Server" error on Windows)
  • #12512: SIGILL (Illegal Instruction) on Intel Xeon E3-1270 V2 (similar CPU compatibility issue on Linux with older CPUs)

All of these appear to be related to the same underlying issue: the binary was rebuilt in v1.1.52-1.1.53 with CPU instructions (likely AVX2) not supported on older processors. The root cause and potential solutions discussed in #12553 may apply to your AMD FX-8350 as well.

Feel free to ignore if your specific case differs.

@github-actions[bot] commented on GitHub (Feb 7, 2026): This issue might be a duplicate of existing issues. Please check: - #12553: Windows: Installer should detect CPU capabilities and use baseline binary for CPUs without AVX2 (discusses the same root cause with Intel CPUs lacking AVX2) - #12521: Bug: After updating to 1.1.53 from 1.1.51, the desktop app doesn't create OpenCode server and fails to start (same "Failed to spawn OpenCode Server" error on Windows) - #12512: SIGILL (Illegal Instruction) on Intel Xeon E3-1270 V2 (similar CPU compatibility issue on Linux with older CPUs) All of these appear to be related to the same underlying issue: the binary was rebuilt in v1.1.52-1.1.53 with CPU instructions (likely AVX2) not supported on older processors. The root cause and potential solutions discussed in #12553 may apply to your AMD FX-8350 as well. Feel free to ignore if your specific case differs.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label bug web windows
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8800
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?