Skip to content

Conversation

@shanevcantwell
Copy link
Contributor

@shanevcantwell shanevcantwell commented Feb 12, 2026

Summary

  • Pass pre-read content from overrideAssistantFile through the PackageIdentifier in LocalProfileLoader, reusing the content bypass added to RegistryClient in PR fix: pass pre-read content to RegistryClient for WSL compatibility #9739
  • Check for pre-read content before the fs.existsSync gate in doLoadConfig, preventing fallback to the deprecated JSON config loader when the YAML path can't be resolved cross-filesystem

Context

When VS Code runs on Windows host with a WSL remote workspace (extensionKind: ["ui", "workspace"]), selecting an agent config from .continue/agents/ fails with:

Failed to parse config.json: Error: ENOENT: no such file or directory, open 'C:\Users\<user>\.continue\config.json'

localPathOrUriToPath can't resolve vscode-remote:// URIs to local paths on the Windows host, so fs.existsSync returns false, falling through to the deprecated JSON loader. The content is already available in memory — it just wasn't being passed through.

Same class of issue as #6242, #7810 (fixed in #9739) and #9661 (fixed in #9679).

Fixes #10450

Test plan

  • New unit tests: LocalProfileLoader passes content in packageIdentifier for override files
  • New unit tests: doLoadConfig uses YAML loading (not JSON fallback) when pre-read content is available
  • All 1654 existing core tests pass
  • All 291 config-yaml package tests pass
  • Manual: select agent config from .continue/agents/ in WSL remote workspace

🤖 Generated with Claude Code


Summary by cubic

Pass pre-read YAML content from override agent files to the config loader to avoid fs.existsSync checks for vscode-remote URIs. This fixes agent config selection in VS Code on Windows with a WSL remote workspace.

  • Bug Fixes
    • LocalProfileLoader includes overrideAssistantFile.content in PackageIdentifier to reuse the content bypass path.
    • doLoadConfig checks for pre-read content before fs.existsSync and uses the YAML loader when present, avoiding fallback to the deprecated JSON loader when paths aren’t resolvable across Windows/WSL.

Written for commit f9714fe. Summary will update on new commits.

When VS Code runs on Windows host with a WSL remote workspace, selecting
an agent config from .continue/agents/ fails because localPathOrUriToPath
cannot resolve the vscode-remote:// URI to a local path, causing
fs.existsSync to return false and falling through to the deprecated JSON
config loader.

The fix passes pre-read content (already available in
overrideAssistantFile.content) through the PackageIdentifier, and checks
for it before the fs.existsSync gate. This reuses the content bypass
added to RegistryClient in PR continuedev#9739.

Fixes continuedev#10450

Co-Authored-By: Claude Opus 4.6 <[email protected]>
@shanevcantwell shanevcantwell requested a review from a team as a code owner February 12, 2026 00:43
@shanevcantwell shanevcantwell requested review from sestinj and removed request for a team February 12, 2026 00:43
@dosubot dosubot bot added the size:L This PR changes 100-499 lines, ignoring generated files. label Feb 12, 2026
Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 4 files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:L This PR changes 100-499 lines, ignoring generated files.

Projects

Status: Todo

Development

Successfully merging this pull request may close these issues.

Agent config loading falls back to config.json on Windows host with WSL remote

1 participant