38aae62e56
Fixes #6242, #7810 When Windows VS Code connects to WSL, workspace files are accessed via vscode-remote:// URIs. Previously, getAllDotContinueDefinitionFiles() correctly read content via ide.readFile(), but loadYaml.ts discarded the content and passed only the URI path to RegistryClient, which then tried to re-read using fs.readFileSync() - failing for remote URIs. Changes: - Add optional content field to FileIdentifier (non-breaking) - RegistryClient.getContent() returns pre-read content when present - loadYaml.ts passes content along with file identifiers Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Continue
Ship faster with Continuous AI
The future of coding isn't writing more code. It's delegating the boring parts, so you can build the interesting stuff
Get started in Mission Control, CLI (Headless Mode), or CLI (TUI mode)
Quick Install
npm i -g @continuedev/cli
cn
Cloud Agents
Set workflows to run automatically on PR opens, schedules, or any event trigger
CLI Agents
Watch workflows execute in real-time and approve decisions step-by-step from your terminal
IDE Agents
Trigger workflows from VS Code or JetBrains—let agents handle the refactoring while you keep coding
Contributing
Read the contributing guide, and join the GitHub Discussions.