Docs cannot be added with Ubuntu on WSL (Windows 11)

[fctlb]

Before submitting your bug report

• I believe this is a bug. I'll try to join the Continue Discord for questions
• 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: Ubuntu on WSL (Windows 11)
- Continue version: 1.0.14
- IDE version: VS Code 1.101.1
- Model: gemma3:latest (from Ollama)
- workspace/.continue/docs/new_doc.yaml:
  
name: New doc
version: 0.0.1
schema: v1
docs:
  - name: New docs
    startUrl: https://docs.continue.dev

Description

YAML file exists in .continue/docs directory in my workspace, but can't be read. This might be some path issue specific to Windows + WSL, but I cannot come up with a resolution. Can Continue.dev handle it by itself?

ENOENT: no such file or directory, open 'C:\Users\chaud\AppData\Local\Programs\Microsoft VS Code\vscode-remote:\wsl%2Bubuntu\mnt\e\project\.continue\docs\new-doc.yaml'.
> vscode-remote://wsl%2Bubuntu/mnt/e/project/.continue/docs/new-doc.yaml

To reproduce

1. Setup Ubuntu on WSL and Connect VS Code with It
2. Setup Ollama and pull gemma3:latest model
3. Try to setup any documentation

Log output

[sestinj]

Thanks for sharing this @fctlb. I think we saw this earlier this week and are working on solving it, if there's not already a PR. @jpoly1219 I think you would know the status of this, could you share whatever extra context you have here?

[jpoly1219]

This is reproducible on my machine when I use local assistant (which matches @fctlb 's setup).

The paths seem to be valid actually -- C:\Users\username\AppData\Local\Programs\Microsoft VS Code\ is where vscode is installed on windows. Then the rest of it signifies a bridge to vscode's remote server. The issue is that Node has no idea how to interpret this. I think this is a mix of vscode-specific methods and node-specific methods clashing, and we need to do some more thorough checks and programmatic path resolution when we detect the target system is running WSL.

However it's pretty difficult to test this on WSL because:

• running the extension in debug mode solves this because the filepaths correctly resolve to linux paths somehow.
• running npm run package inside wsl gives us a linux build, which doesn't install properly on windows
• setting the build target to win32 does not work, it automatically reverts back to linux. I think it has to do with how it's prepackage that's actually being ran, not package.
• changing the build script to always use win32 doesn't work because some dependencies (I think it was sqlite3) fails to build)

[jpoly1219]

@sestinj if you can help me figure out the build script inside extensions/vscode then I can take this 👍

[fctlb]

@jpoly1219 is there a way I can enabled using the extension (the debug mode you mentioned about), this is currently a blocker for some learning tutorials and documentation I am working on

CC: @sestinj

[jpoly1219]

@fctlb what you could do (and tell me if this works) is:

• Add .continue/docs/your_docs.md in your project repo.
• Clone the Continue repo and do the initial setups listed in CONTRIBUTING.md
• Change the launch.json to open up to the directory you are working in.
• Launch in debug mode.

Let me know how that goes!

[mitgobla]

I also receive the ENOENT: no such file or directory error when configuring an MCP server that is on the WSL instance.

'D:\Program Files\Microsoft VS Code\vscode-remote:\wsl%2Bubuntu\home\USERNAME\iot-mcp-project\.continue\mcpServers\new-mcp-server.yaml'.
> vscode-remote://wsl%2Bubuntu/home/USERNAME/iot-mcp-project/.continue/mcpServers/new-mcp-server.yaml

[Merieli]

I have the same problem when trying to run the locally configured MCPs within my project in .continue/mcpServers.

Explanation: My current project is within the WSL environment, and VS Code is installed on Windows. I have the following error:

ENOENT: no such file or directory, open 'C:\Users\merie\AppData\Local\Programs\Microsoft VS Code\vscode-remote:\wsl%2Bdebian\home\merieli\projects\meraki-shop\.continue\mcpServers\playwright-mcp.yaml'. > vscode-remote://wsl%2Bdebian/home/merieli/projects/meraki-shop/.continue/mcpServers/playwright-mcp.yaml

In other words, the extension can't resolve the path to the .continue settings within a project that exists within WSL.

Any estimate for when we'll have this fix?

[jballn]

Yeah me too, the docs feature just doesn't work without sorting this out

`'C:\Users\John Allen\AppData\Local\Programs\Microsoft VS Code\vscode-remote:\wsl%2Bubuntu\home\dev\jabba\portcullis.continue\docs\radius-server-reference.yaml'.

vscode-remote://wsl%2Bubuntu/home/dev/jabba/portcullis/.continue/docs/radius-server-reference.yaml`

[NicolaSpreafico]

I'm getting the same problem, trying to define prompts/myprompt.yamml and the path is wrong as other users