You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actually, this says it is clean. You have barely any detections. And any detections it gets are from noname AVs or known problematic ones like google or windows
Actually, this says it is clean. You have barely any detections. And any detections it gets are from noname AVs or known problematic ones like google or windows
Clean means no detections. Your powers of observation are flawed, as are your dismissals.
Activity
github-actions commentedon Jan 11, 2026
This issue might be a duplicate of existing issues. Please check:
Trojan:Win32/Wacatac.H!mlwhen running opencode #7592: [False Positive?] Windows Defender detectsTrojan:Win32/Wacatac.H!mlwhen running opencodeFeel free to ignore if none of these address your specific case.
PRIMExALBIN commentedon Jan 11, 2026
magicprinc commentedon Jan 11, 2026
+1 on Windows 10
alanmcilwaine commentedon Jan 11, 2026
+1 on Windows 11. Multiple people on our team can reproduce it by installing v1.1.13 via npm and running opencode.
Akinue commentedon Jan 11, 2026
+1 on Windows 11. Tried install via Chocolatey v1.1.13
opencode 1.1.13 Downloading opencode 64 bit from 'https://github.com/anomalyco/opencode/releases/download/v1.1.13/opencode-windows-x64.zip' Progress: 100% - Completed download of C:\Users\user\AppData\Local\Temp\chocolatey\opencode\1.1.13\opencode-windows-x64.zip (49.47 MB). Download of opencode-windows-x64.zip (49.47 MB) completed. Hashes match. Extracting C:\Users\user\AppData\Local\Temp\chocolatey\opencode\1.1.13\opencode-windows-x64.zip to C:\ProgramData\chocolatey\lib\opencode\tools... C:\ProgramData\chocolatey\lib\opencode\tools Added C:\ProgramData\chocolatey\bin\opencode.exe shim pointed to '..\lib\opencode\tools\opencode.exe'.For completeness sake I was on 1.1.7 and uninstalled to re-install the update. Just tested 1.1.12, 1.1.11, 1.1.10 same behavior.
1.1.7, 1.1.8 work fine from chocolately (1.1.9 doesn't exist).
ricred commentedon Jan 11, 2026
+1 on Windows 11. Tried install via Chocolatey v1.1.11
okazakov commentedon Jan 11, 2026
Another issue raised for this here: #7669
uoyoCsharp commentedon Jan 12, 2026
+1 on Windows 11. downloaded the installation package from the official website on 2026/01/12.
BumpyClock commentedon Jan 12, 2026
+1
Mirrowel commentedon Jan 12, 2026
Actually, this says it is clean. You have barely any detections. And any detections it gets are from noname AVs or known problematic ones like google or windows
jackheuberger commentedon Jan 12, 2026
+1 installed from bun
rekram1-node commentedon Jan 12, 2026
Going to do some code signing stuff to prevent these false positives
4cecoder commentedon Jan 12, 2026
cloning the project trying to run from source and windows seems to remove this
opentui package may be the issue on windows getting flagged?
it seems the opentui might be:
sus
Vagenda commentedon Jan 14, 2026
Clean means no detections. Your powers of observation are flawed, as are your dismissals.
odiseo0 commentedon Feb 4, 2026
+1 on 1.1.51
ShanQincheng commentedon Feb 5, 2026
+1 on 1.1.51
Hona commentedon Mar 29, 2026
As of OpenCode v1.3.4 across the CLI + Desktop apps, we have full code signing - so there should be no more warnings.
Please let me know otherwise