Continue VS Code extension fails to start MCP servers in WSL workspaces (looks for cmd.exe inside Ubuntu) #9151
Description
Before submitting your bug report
- I've tried using the "Ask AI" feature on the Continue docs site to see if the docs have an answer
- I'm not able to find a related conversation on GitHub discussions that reports the same bug
- I'm not able to find an open issue that reports the same bug
- I've seen the troubleshooting guide on the Continue Docs
Relevant environment info
- OS: Windows 11
- Continue version:
1.2.11
- IDE version: 1.107.0
- Model: quen3-coder.480b-cloud
- config:
name: Local Config
version: 1.0.0
schema: v1
models:
- name: qwen3-coder:480b-cloud
provider: ollama
model: qwen3-coder:480b-cloud
apiBase: http://localhost:11434
roles:
- apply
- chat
- edit
capabilities:
- tool_use
- name: qwen3-vl:235b-cloud
provider: ollama
model: qwen3-vl:235b-cloud
apiBase: http://localhost:11434
roles:
- apply
- chat
- edit
capabilities:
- tool-use
- name: gpt-oss:120b-cloud
provider: ollama
model: gpt-oss:120b-cloud
apiBase: http://localhost:11434
roles:
- apply
- chat
- edit
capabilities:
- tool-use
- name: qwen3-vl:8b
provider: ollama
model: qwen3-vl:8b
apiBase: http://localhost:11434
roles:
- apply
- chat
- edit
capabilities:
- tool-use
- name: deepseek-v3.1:671b-cloud
provider: ollama
model: deepseek-v3.1:671b-cloud
apiBase: http://localhost:11434
roles:
- apply
- chat
- edit
capabilities:
- tool-use
- name: Autodetect
provider: ollama
model: AUTODETECT
capabilities:
- tool_use
roles:
- chat
- edit
- apply
- rerank
- autocomplete
mcpServers:
- name: Chrome DevTools
command: npx
args:
- -y
- chrome-devtools-mcp@latest
- name: Context7 MCP
type: streamable-http
url: https://mcp.context7.com/mcp
- name: Fetch
command: uvx
args:
- mcp-server-fetch
- name: Filesystem
command: npx
args:
[
"-y",
"@modelcontextprotocol/server-filesystem",
"/home/nathaniel/projects",
"/home/nathaniel/Documents/Projects",
]
- name: Git
command: uvx
args:
- mcp-server-git
- name: ImageSocery
command: /home/nathaniel/projects/venv/imagesorcery-mcp/.venv/bin/python
args:
- -m
- imagesorcery_mcp.server
- --transport
- stdio
autoApprove:
[
"blur",
"change_color",
"crop",
"detect",
"draw_arrows",
"draw_circles",
"draw_lines",
"draw_rectangles",
"draw_texts",
"fill",
"find",
"get_metainfo",
"ocr",
"overlay",
"resize",
"rotate",
]
- name: Kubernetes
command: npx
args:
- -y
- kubernetes-mcp-server@latest
- name: Playwright
command: npx
args: ["@playwright/mcp@latest", "--headless"]
- name: Podman
command: npx
args:
- -y
- podman-mcp-server@latest
- name: Sequential Thinking
command: npx
args: ["-y", "@modelcontextprotocol/server-sequential-thinking"]
OR link to agent in Continue hub:Description
When opening a project in VS Code using WSL (Ubuntu), the Continue VS Code extension fails to start any MCP servers. Each MCP server reports an error similar to:
Failed to connect to ""
Error: command "cmd.exe" not found. To use this MCP server, install the cmd.exe CLI.
This occurs only for WSL projects. The same Continue configuration and MCP servers load correctly when opening a non-WSL (Windows) project.
Expected behavior
When working in a WSL workspace, Continue should either:
Run MCP servers inside the WSL environment (using bash / Linux paths), or
Clearly document that MCP servers are not supported in WSL and gracefully disable them
The extension should not attempt to invoke cmd.exe when the workspace is running in Ubuntu WSL.
Actual behavior
Continue appears to:
Run the extension on Windows even when a WSL workspace is active
Attempt to spawn MCP servers using Windows shell assumptions
Fail because cmd.exe does not exist inside WSL
Additional details
Continue CLI works correctly when run directly inside Ubuntu WSL using the Linux config.yaml
The VS Code Continue extension appears to always use the Windows-side config and shell, even for WSL workspaces
There is no visible “Install in WSL” option for the Continue extension (unlike many other VS Code extensions)
This makes MCP unusable for WSL-based development
There is no visible “Install in WSL” option for the Continue extension (unlike many other VS Code extensions)
Steps to reproduce
Install Continue VS Code extension on Windows
Configure MCP servers (e.g., Chrome-Devtools, filesystem, etc.)
Open a project located in WSL (\wsl$ or “Open Folder in WSL”)
Observe MCP server startup failures referencing cmd.exe
Open a Windows-based project
Observe MCP servers load correctly
This makes MCP unusable for WSL-based development
Question / Request
Is WSL officially supported for MCP servers in the Continue VS Code extension?
If not, could:
MCP servers be disabled automatically in WSL, or
The extension support running MCP servers inside the WSL extension host?
If not, could:
MCP servers be disabled automatically in WSL, or
The extension support running MCP servers inside the WSL extension host?
To reproduce
No response