anomalyco / anomalyco/opencode

Windows CLI hangs after model selection, while Web UI works normally

Open
#39,859 1 comment 0 reactions 1 assignee View on GitHub

@Hona is already working on this.

Since Jul 31, 2026.

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

Description

Description

Windows CLI hangs after model selection, while Web UI works normally

Environment
  • OS: Windows 11
  • Node.js: v24.14.1
  • pnpm: v11.18.0 (via Corepack)
  • OpenCode: v1.18.10
Problem

The Web UI works correctly and can generate responses.

However, the CLI hangs indefinitely when running:

opencode run "hello"

or

opencode run "hello" --pure --print-logs --log-level DEBUG

No response is ever returned.

Debug logs

The logs always stop after model selection:

message=stream providerID=opencode modelID=deepseek-v4-flash-free
message="llm runtime selected" llm.runtime=ai-sdk llm.provider=opencode llm.model=deepseek-v4-flash-free

Nothing is printed after this, even after waiting several minutes.

The same behavior previously occurred with:

big-pickle
Things I already tried
  • Fresh installation
  • Removed and reinstalled OpenCode
  • Switched to Corepack-managed pnpm
  • --pure mode
  • Different default models
  • Verified internet connectivity
  • Web UI works normally on the same machine
Expected behavior

opencode run "hello" should return a response in the terminal.

Actual behavior

The CLI hangs forever after selecting the model, while the Web UI continues to function normally.

Please let me know if you'd like me to test a nightly build or provide additional logs.

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

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.