config.yaml not finding schema

[StephaneAdeso]

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: Windows 11 pro (Windows_NT x64 10.0.26100)
- Continue version: 1.0.8
VSCODE Version: 1.99.3 (user setup)
Commit: 17baf841131aa23349f217ca7c570c76ee87b957
Date: 2025-04-15T23:18:46.076Z
Electron: 34.3.2
ElectronBuildId: 11161073
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
- config:
  
name: Local Assistant
version: 1.0.0
schema: v1
models: []
context:
  - provider: code
  - provider: docs
  - provider: diff
  - provider: terminal
  - provider: problems
  - provider: folder
  - provider: codebase
  
  OR link to assistant in Continue hub:

Description

The config.yaml display the following error:

Unable to load schema from 'c:\Users\<user>\.vscode\extensions\continue.continue-1.0.7-win32-x64\config-yaml-schema.json': No content

Even if you delete the config.yaml and .json, and open vscode to regenerate the file, the error still there.

I think the issue is that it is looking for the \continue.continue-1.0.7 path, but after updating continue extension, now everything is in the \continue.continue-1.0.8 folder.

To reproduce

1. Delete all youre config files.
2. Close VSCode and reopen it.
3. Open the continue extension so the config.yaml is create from new.
4. Open the config.yaml

Log output

[drcrallen]

I had the same issue.

This can be worked around in vscode by going to Ctrl-P > Preferences: Open User Settings (JSON) and changing your yaml.schemas to point to the valid file.

The bug seems to be that this setting isn't changed as versions update.

[ikario404]

@drcrallen tried it but it wont worked. Tried then uninstall/reinstall but wont worked neither (it updated correctly filename path thought)

[RomneyDa]

Thanks all for the report. Fixed here
#5851

[2vn9s1c]

This keeps causing problems with every update, requiring time to manually repair the issue. Is this just me?
OS: Ubuntu - Pop_OS!

[2vn9s1c]

This update was made again, it's broken again, and I have to invest time and effort into fixing this.
Am I really the only one this is happening to?