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
{{ message }}
Repository navigation
[macOS] Critical: App killed on startup after update due to "Code Signature Invalid" #9939
After updating to the latest version, opencode fails to start on macOS. The process is immediately killed by the OS.
To Reproduce
Update opencode to the latest version.
Run opencode in terminal.
Output:
[1] 10549 killed opencode
Root Cause Analysis (Logs)
Using sudo dmesg, I captured the kernel logs which confirm a Code Signing issue. The binary signature seems to be invalid or quarantined after the update.
Plaintext
[72909.498110]: proc 10073: load code signature error 2 for file "opencode"
[72909.498442]: ASP: Security policy would not allow process: 10073, /Users/USER/.opencode/bin/opencode
Working Solution
I fixed it by manually removing the quarantine attribute and forcing a re-sign of the binary:
These issues all report the same symptom: opencode process being killed on macOS without clear error messages. The root cause analysis in this issue (code signature errors from dmesg logs) provides valuable technical detail that could help resolve all three issues.
Feel free to ignore if your specific case differs from these existing reports.
Confirming the same issue. After installing the CLI through the Desktop menu, I also encountered zsh: killed opencode.
Upon inspection, it was found that ~/.opencode/bin/opencode lacks a code signature:
Running codesign -v ~/.opencode/bin/opencode shows that it is unsigned.
Temporary solution:
Run sudo codesign --force --deep --sign - ~/.opencode/bin/opencode.
Suggestion: The OpenCode release process should ensure that all distribution channels (installation scripts, Desktop, npm, and auto-updates) provide binaries with proper code signing.
Activity
github-actions commentedon Jan 22, 2026
This issue might be a duplicate of existing issues. Please check:
These issues all report the same symptom: opencode process being killed on macOS without clear error messages. The root cause analysis in this issue (code signature errors from dmesg logs) provides valuable technical detail that could help resolve all three issues.
Feel free to ignore if your specific case differs from these existing reports.
philfan02 commentedon Jan 25, 2026
This worked perfectly for me, thank you!
loocor commentedon Mar 4, 2026
Confirming the same issue. After installing the CLI through the Desktop menu, I also encountered
zsh: killed opencode.Upon inspection, it was found that
~/.opencode/bin/opencodelacks a code signature:Running
codesign -v ~/.opencode/bin/opencodeshows that it is unsigned.Temporary solution:
Run
sudo codesign --force --deep --sign - ~/.opencode/bin/opencode.Suggestion: The OpenCode release process should ensure that all distribution channels (installation scripts, Desktop, npm, and auto-updates) provide binaries with proper code signing.
ramarivera commentedon Mar 8, 2026
+1ing this, thanks for raising the issue!
EDIT: On second look, I ran the codesign and it still does not work for me and there are no logs whatsover that can be useful
johnsonsleo commentedon Apr 20, 2026
same issue
github-actions commentedon Jul 6, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.