anomalyco / anomalyco/opencode

[BUG]: Windows Desktop sidecar crashes with exitCode -2147483645, then "Failed to fetch"

Open
#41,714 3 comments 0 reactions 1 assignee View on GitHub

@Hona is already working on this.

Since Aug 11, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

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).

opencode-OC-Test-logs.zip

Plugins

None

OpenCode version

1.18.15 and 1.18.16

Steps to reproduce
  1. Create an empty local directory: C:\OC-Test
  2. Open C:\OC-Test as a project in OpenCode Desktop.
  3. Wait for the local server to start.
  4. After a short time, session loading fails with "Failed to fetch".
  5. utility.log shows that the opencode server sidecar crashed with exitCode -2147483645.
Screenshot and/or share link
Image
Operating System

Windows 11 Business 24H2 (OS Build 26100.8893)

Terminal

Windows PowerShell

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.