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

After upgrading to the latest version of OpenCode, it won't respond/open. Help!! #8776

New Issue
Open
opened 2026-02-16 18:10:49 -05:00 by yindo · 15 comments
yindo commented 2026-02-16 18:10:49 -05:00
Owner
Copy Link
Copy Source

Originally created by @freewinder-tech on GitHub (Feb 7, 2026).

Originally assigned to: @rekram1-node on GitHub.

Question

I just updated to the latest version of OpenCode（v1.1.53），my os is win10, but now it won't launch. Clicking the icon does nothing, and there's no output when running the command in PowerShell or CMD. Any help would be appreciated!

Originally created by @freewinder-tech on GitHub (Feb 7, 2026). Originally assigned to: @rekram1-node on GitHub. ### Question I just updated to the latest version of OpenCode（v1.1.53），my os is win10, but now it won't launch. Clicking the icon does nothing, and there's no output when running the command in PowerShell or CMD. Any help would be appreciated!
yindo added the windows label 2026-02-16 18:10:49 -05:00
yindo commented 2026-02-16 18:10:49 -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:

  • #11236: opencode command cli cannot be started (Windows PowerShell, similar upgrade issue with no response)
  • #11322: Everything goes blank on launching -Update (Windows 11, blank screen after launch)
  • #7919: Windows Defender reports Trojan when launching OpenCode (Windows security issue preventing launch)
  • #7810: Opencode will not launch if you set Agent permissions as True/False (Windows, won't launch after upgrade)
  • #5485: Opencode become stuck all of a sudden. Does not launch anymore (Windows, launch issue with blank screen)

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

@github-actions[bot] commented on GitHub (Feb 7, 2026): This issue might be a duplicate of existing issues. Please check: - #11236: opencode command cli cannot be started (Windows PowerShell, similar upgrade issue with no response) - #11322: Everything goes blank on launching -Update (Windows 11, blank screen after launch) - #7919: Windows Defender reports Trojan when launching OpenCode (Windows security issue preventing launch) - #7810: Opencode will not launch if you set Agent permissions as True/False (Windows, won't launch after upgrade) - #5485: Opencode become stuck all of a sudden. Does not launch anymore (Windows, launch issue with blank screen) Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 18:10:49 -05:00
Author
Owner
Copy Link
Copy Source

@freewinder-tech commented on GitHub (Feb 7, 2026):

D:\op-test>opencode run hello --print-logs

D:\op-test>
no response

@freewinder-tech commented on GitHub (Feb 7, 2026): D:\op-test>opencode run hello --print-logs D:\op-test> no response
yindo commented 2026-02-16 18:10:49 -05:00
Author
Owner
Copy Link
Copy Source

@Casperlet commented on GitHub (Feb 7, 2026):

Me too.

Please rollback the opencode to the old version 1.1.51. It works again now.

@Casperlet commented on GitHub (Feb 7, 2026): Me too. Please rollback the opencode to the old version 1.1.51. It works again now.
yindo commented 2026-02-16 18:10:49 -05:00
Author
Owner
Copy Link
Copy Source

@Afonsojr commented on GitHub (Feb 7, 2026):

Title: OpenCode crashes with STATUS_ILLEGAL_INSTRUCTION on older Intel CPUs (pre-Haswell)

Description:

OpenCode fails to run on systems with older Intel processors (Ivy Bridge and earlier) due to the use of CPU instructions not supported by these processors. The application crashes immediately without any error message or output.

Environment:
• OS: Windows 11 (Build 22631)
• CPU: Intel Core (Ivy Bridge, Family 6 Model 58) - 3rd Generation
• Architecture: x64 (AMD64)
• Shell: PowerShell 7.5.4
• OpenCode Version: v1.1.53 (affected), v1.1.30 (works)

Steps to Reproduce:

  1. Install OpenCode v1.1.53 on a system with an Intel Ivy Bridge (or older) processor
  2. Run opencode --version or opencode
  3. The application exits immediately with no output

Expected Behavior:
OpenCode should start normally or display a clear error message about CPU compatibility.

Actual Behavior:
The application crashes silently. When run from terminal, it returns exit code -1073741795 (0xC000007D = STATUS_INVALID_IMAGE_FORMAT) or -1073741510.

Windows Event Log Analysis:
Root Cause:
The exception code 0xc000001d (STATUS_ILLEGAL_INSTRUCTION) indicates that the binary contains CPU instructions not supported by the processor. This is likely due to the binary being compiled with AVX2 or other instruction set extensions introduced in Intel Haswell (4th gen, 2013) or later.

Workaround:
Downgrading to version v1.1.30 resolves the issue. This suggests that newer versions introduced compiler optimizations targeting modern CPUs.

Version Bisect:
• v1.1.30: ✅ Works
• v1.1.53: ❌ Crashes

Suggested Fix:
Consider one of the following approaches:

  1. Compile release binaries with a baseline x86-64 instruction set (SSE2/SSE3) without AVX2
  2. Provide separate binaries for legacy CPUs (e.g., opencode-windows-x64-legacy.zip)
  3. Use runtime CPU feature detection to provide a meaningful error message

Additional Context:
• The binary is correctly identified as x64 PE format
• Visual C++ Redistributable 14.44 is installed
• WebView2 Runtime 144.0.3719.115 is installed
• The issue affects Scoop installations as well as direct downloads from GitHub releases

@Afonsojr commented on GitHub (Feb 7, 2026): Title: OpenCode crashes with STATUS_ILLEGAL_INSTRUCTION on older Intel CPUs (pre-Haswell) Description: OpenCode fails to run on systems with older Intel processors (Ivy Bridge and earlier) due to the use of CPU instructions not supported by these processors. The application crashes immediately without any error message or output. Environment: • OS: Windows 11 (Build 22631) • CPU: Intel Core (Ivy Bridge, Family 6 Model 58) - 3rd Generation • Architecture: x64 (AMD64) • Shell: PowerShell 7.5.4 • OpenCode Version: v1.1.53 (affected), v1.1.30 (works) Steps to Reproduce: 1. Install OpenCode v1.1.53 on a system with an Intel Ivy Bridge (or older) processor 2. Run opencode --version or opencode 3. The application exits immediately with no output Expected Behavior: OpenCode should start normally or display a clear error message about CPU compatibility. Actual Behavior: The application crashes silently. When run from terminal, it returns exit code -1073741795 (0xC000007D = STATUS_INVALID_IMAGE_FORMAT) or -1073741510. Windows Event Log Analysis: Root Cause: The exception code 0xc000001d (STATUS_ILLEGAL_INSTRUCTION) indicates that the binary contains CPU instructions not supported by the processor. This is likely due to the binary being compiled with AVX2 or other instruction set extensions introduced in Intel Haswell (4th gen, 2013) or later. Workaround: Downgrading to version v1.1.30 resolves the issue. This suggests that newer versions introduced compiler optimizations targeting modern CPUs. Version Bisect: • v1.1.30: ✅ Works • v1.1.53: ❌ Crashes Suggested Fix: Consider one of the following approaches: 1. Compile release binaries with a baseline x86-64 instruction set (SSE2/SSE3) without AVX2 2. Provide separate binaries for legacy CPUs (e.g., opencode-windows-x64-legacy.zip) 3. Use runtime CPU feature detection to provide a meaningful error message Additional Context: • The binary is correctly identified as x64 PE format • Visual C++ Redistributable 14.44 is installed • WebView2 Runtime 144.0.3719.115 is installed • The issue affects Scoop installations as well as direct downloads from GitHub releases
yindo commented 2026-02-16 18:10:49 -05:00
Author
Owner
Copy Link
Copy Source

@freewinder-tech commented on GitHub (Feb 7, 2026):

npm install -g opencode-ai@1.1.51，after install ,its version is 1.1.51,but after run opencode,exit,version auto upgrade to 1.1.53,run opencode no response again.

@freewinder-tech commented on GitHub (Feb 7, 2026): npm install -g opencode-ai@1.1.51，after install ,its version is 1.1.51,but after run opencode,exit,version auto upgrade to 1.1.53,run opencode no response again.
yindo commented 2026-02-16 18:10:49 -05:00
Author
Owner
Copy Link
Copy Source

@BassemN commented on GitHub (Feb 8, 2026):

I am using Ubuntu 20.04.6 LTS. Opencode was running properly on version 1.1.51, but after upgrading to version 1.1.52 or 1.1.53, it no longer runs.

@BassemN commented on GitHub (Feb 8, 2026): I am using Ubuntu 20.04.6 LTS. Opencode was running properly on version 1.1.51, but after upgrading to version 1.1.52 or 1.1.53, it no longer runs.
yindo commented 2026-02-16 18:10:49 -05:00
Author
Owner
Copy Link
Copy Source

@Casperlet commented on GitHub (Feb 11, 2026):

npm install -g opencode-ai@1.1.51，after install ,its version is 1.1.51,but after run opencode,exit,version auto upgrade to 1.1.53,run opencode no response again.

please edit the opencode.json in the folder ~/.config/opencode, insert the setting "autoupdate": false,, then it will not update again.

@Casperlet commented on GitHub (Feb 11, 2026): > npm install -g opencode-ai@1.1.51，after install ,its version is 1.1.51,but after run opencode,exit,version auto upgrade to 1.1.53,run opencode no response again. please edit the `opencode.json` in the folder `~/.config/opencode`, insert the setting `"autoupdate": false,`, then it will not update again.
yindo commented 2026-02-16 18:10:49 -05:00
Author
Owner
Copy Link
Copy Source

@adamdotdevin commented on GitHub (Feb 12, 2026):

@Afonsojr @BassemN @Casperlet @freewinder-tech can you upgrade to latest (1.1.64) and let me know if this is resolved?

@adamdotdevin commented on GitHub (Feb 12, 2026): @Afonsojr @BassemN @Casperlet @freewinder-tech can you upgrade to latest (1.1.64) and let me know if this is resolved?
yindo commented 2026-02-16 18:10:49 -05:00
Author
Owner
Copy Link
Copy Source

@BassemN commented on GitHub (Feb 12, 2026):

@adamdotdevin Unfortunately, in my case, the issue is still there even in version 1.1.63.

@BassemN commented on GitHub (Feb 12, 2026): @adamdotdevin Unfortunately, in my case, the issue is still there even in version 1.1.63.
yindo commented 2026-02-16 18:10:49 -05:00
Author
Owner
Copy Link
Copy Source

@adamdotdevin commented on GitHub (Feb 12, 2026):

@adamdotdevin Unfortunately, in my case, the issue is still there even in version 1.1.63.

sorry, 1.1.64 any better?

@adamdotdevin commented on GitHub (Feb 12, 2026): > [@adamdotdevin](https://github.com/adamdotdevin) Unfortunately, in my case, the issue is still there even in version 1.1.63. sorry, 1.1.64 any better?
yindo commented 2026-02-16 18:10:49 -05:00
Author
Owner
Copy Link
Copy Source

@Casperlet commented on GitHub (Feb 13, 2026):

not work even 1.1.64

@Casperlet commented on GitHub (Feb 13, 2026): not work even 1.1.64
yindo commented 2026-02-16 18:10:49 -05:00
Author
Owner
Copy Link
Copy Source

@BassemN commented on GitHub (Feb 13, 2026):

@adamdotdevin Good news! I can now access Opencode via the terminal after updating to version 1.1.65

@BassemN commented on GitHub (Feb 13, 2026): @adamdotdevin Good news! I can now access Opencode via the terminal after updating to version 1.1.65
yindo commented 2026-02-16 18:10:49 -05:00
Author
Owner
Copy Link
Copy Source

@BassemN commented on GitHub (Feb 13, 2026):

@Casperlet, it worked for me after updating to version 1.1.65. Try updating like I did and see if it resolves the issue.

@BassemN commented on GitHub (Feb 13, 2026): @Casperlet, it worked for me after updating to version 1.1.65. Try updating like I did and see if it resolves the issue.
yindo commented 2026-02-16 18:10:49 -05:00
Author
Owner
Copy Link
Copy Source

@Casperlet commented on GitHub (Feb 13, 2026):

@BassemN yes, the 1.1.65 works, thanks.

@Casperlet commented on GitHub (Feb 13, 2026): @BassemN yes, the 1.1.65 works, thanks.
yindo commented 2026-02-16 18:10:49 -05:00
Author
Owner
Copy Link
Copy Source

@RobLoach commented on GitHub (Feb 13, 2026):

Confirming 1.1.65 fixes it. Nice work!

@RobLoach commented on GitHub (Feb 13, 2026): Confirming 1.1.65 fixes it. Nice work!
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 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#8776
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?