Continue v1.2.14 does not report a missing YAML extension anywhere that's easily seen

[dannypike]

Before submitting your bug report

• I've tried using the "Ask AI" feature on the Continue docs site to see if the docs have an answer
• I'm not able to find a related conversation on GitHub discussions that reports the same bug
• 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

Continue v1.2.14

Description

The YAML extension is a hidden dependency that should be documented or auto-installed
Continue silently fails to read config.yaml without it
The error only appears in the Extension Host logs, not in a user-visible location

I know that everyone eventually install YAML but, on a new PC, it's easily forgotten until you need it for something.

Continue should either:

List the YAML extension as a dependency (so VS Code auto-installs it)
Show a user-friendly error message when the YAML extension is missing
Support the config without requiring the YAML extension

To reproduce

1. Buy a new PC
2. Install VS Code
3. Install Ollama
4. Install Continue
5. Try to get Continue to talk to your custom Ollama Modelfile

It won't read the config.yaml regardless of how much you scream at the keyboard. The problem is buried in the Console Log output of the internal browser for VSCode's Electron.

Log output

I'm not going to paste the whole log file here because it would take too long to cut out the private stuff, but he's what I think the key line is:

"Failed to register Continue config.yaml schema, most likely, YAML extension is not installed"

[RomneyDa]

@dannypike the YAML extension is not required for continue to read and parse YAML files, it's only for users to have syntax highlighting and suggestions in config.yaml files.

Failed to register Continue config.yaml schema means users will not get this nicety but will not cause Continue to fail YAML reading.

[dannypike]

Thanks for the quick response. I think that something else is broken on this machine, then. Please ignore this error, with my apologies for taking your time.