anomalyco / anomalyco/opencode

Severe sluggishness in OpenCode Desktop on Windows (even with OpenCode Go)

Open
#39,251 3 comments 2 reactions 1 assignee View on GitHub

@Hona is already working on this.

Since Jul 28, 2026.

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

Description

Description

I am experiencing severe, unusable sluggishness when using OpenCode on Windows. The extreme lag occurs even though I am subscribed to the OpenCode Go API.

Initially, I thought this was a UI rendering issue in the Desktop app, but I have confirmed that the OpenCode CLI is equally slow. This suggests the bottleneck is at the engine level (possibly file I/O indexing loops or network/proxy timeouts), rather than just the DOM rendering.

I have already tried the following without success:

  1. Completely uninstalled and reinstalled the application multiple times.
  2. Deleted local session caches and storage (%USERPROFILE%\.local\share\opencode).
  3. Tested the CLI directly.
Steps to Reproduce
  1. Open Opencode
  2. in the chat window type anything it takes 1-2min to Thinking to come
  3. Thinking takes another 1-2min to respond
Expected Behavior

OpenCode Desktop and CLI should remain responsive, and OpenCode Go API requests should process quickly without freezing the application or terminal.

Actual Behavior

The application and CLI are extremely slow, laggy, and unresponsive, making it practically unusable.

System Information
  • OS: Windows [ 11]
  • Subscription Type: OpenCode Go
  • Hardware Specs: [32GB RAM, Ryzen 5000 processor]
  • Antivirus/Proxy: [Default Windows Defender, No VPN / Company VPN]
Additional Context

Since deleting .local/share/opencode and trying the CLI didn't resolve the lag, the issue seems to persist independently of the desktop UI's cache or rendering engine.

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.