Continue on WSL: ENOENT when adding docs, MCP servers, or prompts in VS Code

Question

Using Continue 1.0.14 in VS Code 1.101.1 on Ubuntu under WSL (Windows 11), adding a documentation YAML from `.continue/docs` fails with `ENOENT: no such file or directory, open 'C:\Users\...\Microsoft VS Code\vscode-remote:\wsl%2Bubuntu\mnt\e\project\.continue\docs
ew-doc.yaml'`. The same error happens for `.continue/mcpServers` and `.continue/prompts` files. How do I get Continue to resolve `.continue` config paths when the project lives in WSL but VS Code is installed on Windows?

AgentArmorHQ team · Accepted Answer

**Status:** Fixed — a maintainer's release bot announced the issue was resolved in `@continuedev/config-yaml` v1.40.0 on 2026-01-31. No user in the thread confirmed the update fixed it for them.

**Root cause:** A contributor reproduced the error with a local assistant and explained that the failing path is the Windows VS Code install directory (`C:\Users\...\Microsoft VS Code\`) joined with the remote-server URI (`vscode-remote://wsl%2Bubuntu/...`). Node cannot interpret this mixed path, so any `.continue` config file inside a WSL project fails with `ENOENT` — the same error appears for `docs/`, `mcpServers/`, and `prompts/` files.

**Workaround from the thread (unconfirmed):** Run the extension in debug mode:
1. Clone the Continue repo and follow the setup steps in `CONTRIBUTING.md`.
2. Keep your YAML files in `.continue/docs/` (or `.continue/mcpServers/`, etc.) inside the project.
3. Change `launch.json` to open the directory you're working in.
4. Launch the extension from the debugger.

A contributor noted debug mode resolves paths correctly to Linux paths; a packaged build from WSL doesn't install properly on Windows (the build script reverts from win32 to linux, and forcing win32 breaks the sqlite3 dependency). No user in the thread confirmed the debug-mode workaround worked for them.

**If still affected:** Verify your install picks up `@continuedev/config-yaml` v1.40.0 or later. That is general advice; the thread only reports which version the issue was marked resolved in.

AgentArmorHQ team · Answer

**What a GitHub user tried on GitHub** (Didn't work)

The reporter created `.continue/docs/new_doc.yaml` in a WSL project and tried to add it as documentation in Continue 1.0.14 (VS Code 1.101.1, Ubuntu on Windows 11), getting `ENOENT: no such file or directory` for the mixed `C:\Users\...\Microsoft VS Code\vscode-remote:\wsl%2Bubuntu\mnt\e\project\.continue\docs
ew-doc.yaml` path.

Source: https://github.com/continuedev/continue/issues/6242

AgentArmorHQ team · Answer

**What @jpoly1219 tried on GitHub** (Worked)

A contributor reproduced the issue and stated that running the extension in debug mode solves it because file paths resolve correctly to Linux paths, though this only applies to debug builds — packaged builds from WSL don't install properly on Windows.

Source: https://github.com/continuedev/continue/issues/6242#issuecomment-3001112327

AgentArmorHQ team · Answer

**What @jpoly1219 tried on GitHub** (Outcome unclear)

A contributor suggested a debug-mode workaround: clone the Continue repo, follow `CONTRIBUTING.md`, change `launch.json` to open your working directory, and launch in debug mode. No user confirmed the result.

Source: https://github.com/continuedev/continue/issues/6242#issuecomment-3011139926

AgentArmorHQ team · Answer

**What @sestinj tried on GitHub** (Worked)

The maintainers' semantic-release bot announced the issue was resolved in `@continuedev/config-yaml` v1.40.0, available on npm and GitHub.

Source: https://github.com/continuedev/continue/issues/6242#issuecomment-3829585300

Continue on WSL: ENOENT when adding docs, MCP servers, or prompts in VS Code

5 answers

Add your answer or comment