Repository navigation
[BUG]: Windows Desktop sidecar crashes with exitCode -2147483645, then "Failed to fetch" #41714
Description
Description
OpenCode Desktop starts normally on Windows and the local server initially becomes available, but after a short time the opencode server sidecar crashes.
The UI then reports TypeError: Failed to fetch.
The issue is reproducible on both 1.18.15 and 1.18.16, including with a completely empty local project outside OneDrive.
The logs show:
sidecar exited { code: 2147483651 }
child process gone {
reason: 'crashed',
exitCode: -2147483645,
serviceName: 'node.mojom.NodeService',
name: 'opencode server'
}
opencode serve works correctly when launched manually, and /global/health returns healthy = True.
I also reinstalled/updated Microsoft Edge WebView2 Runtime, with no change.
GitHub suggested #29599 as a possible duplicate, but that issue reports ACCESS_VIOLATION (0xC0000005) / AttachConsole failures, while this reproduction consistently exits with 0x80000003 (-2147483645).
GitHub also suggested #33069 as a possible duplicate, but that issue reports intermittent ACCESS_VIOLATION (0xC0000005) crashes approximately every 2 days. This issue reproduces within seconds/minutes and consistently exits with 0x80000003 (-2147483645).
Plugins
None
OpenCode version
1.18.15 and 1.18.16
Steps to reproduce
- Create an empty local directory: C:\OC-Test
- Open C:\OC-Test as a project in OpenCode Desktop.
- Wait for the local server to start.
- After a short time, session loading fails with "Failed to fetch".
- utility.log shows that the
opencode serversidecar crashed with exitCode -2147483645.
Screenshot and/or share link
Operating System
Windows 11 Business 24H2 (OS Build 26100.8893)
Terminal
Windows PowerShell
Activity
github-actions commentedon Aug 11, 2026
This issue might be a duplicate of existing issues. Please check:
TypeError: Failed to fetch— same symptom (sidecar crash + renderer connection loss on Windows), though that issue involves a silent death with no exit code logged rather than the specific0x80000003exit code reported here.Annie9682 commentedon Aug 11, 2026
You also suggested #30597. The failure sequence is very similar (sidecar dies → renderer loses connection → Failed to fetch), but in this case utility.log explicitly records the sidecar crash with exitCode -2147483645 (0x80000003) and serviceName: node.mojom.NodeService. The issue is also reproducible within minutes on an empty C:\OC-Test project.
Annie9682 commentedon Aug 13, 2026
Update: After upgrading to OpenCode 1.18.18, the issue is currently no longer reproducible.
Desktop, CLI/TUI, skills and the original workspace are all working normally, and recent logs show no new sidecar crash or Failed to fetch.
I have not changed the workspace configuration or cleaned the old local dependencies.
I’ll keep monitoring and will provide new logs if the issue occurs again.
thdxr commentedon Oct 11, 2026
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (
opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊