anomalyco / anomalyco/opencode

opencode‑cli v1.18.13 freezes after selecting LLM‑runtime inside VS‑Code when CC‑Switch runs for Claude‑Code

Open
#40,676 0 comments 0 reactions 1 assignee View on GitHub

@Hona is already working on this.

Since Aug 5, 2026.

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

Description

Description

Windows environment. When I enable the routing service of CC‑Switch to run Claude‑Code inside VS‑Code, all integrated VS‑Code terminal child‑processes inherit CC‑Switch’s MCP named‑pipe handle.
After I launch opencode‑cli 1.18.13 in the VS‑Code terminal, it hangs right after the prompt "llm runtime selected opencode". No outgoing HTTP request gets sent to the LLM server.
The freeze will not occur when I start opencode‑cli from a standalone native CMD window outside VS‑Code.
I have disabled opencode traffic interception inside CC‑Switch, yet the persistent MCP named‑pipe still triggers the hang‑up during opencode‑cli’s local MCP‑service discovery stage.

Plugins

No response

OpenCode version

1.18.13

Steps to reproduce

1.install vscode & claudecode for vscode plugin
2.use cc swtich config opencode go for claudecode,and open the router
3.npm install opencode cli & opencode for vscode plugin
4.reveals that opencode & claude code can't be co-working in vscode
5.but,the opencode cli works in windows system CMD mode

Screenshot and/or share link

No response

Operating System

windows 11

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.