VS code Continue extension config issue

TL;DR

The reporter found the cause themselves: DeepSeek's API is only compatible with the OpenAI /v1/chat/completions endpoint, not the legacy /v1/completions endpoint. Reporter fixed it by adding "useLegacyCompletionsEndpoint": false to the Continue config.

Steps

1. Issue deepseek-ai/awesome-deepseek-integration#11 (closed, 9 comments): VS Code Continue extension hit a 404 against the DeepSeek API. The reporter found the cause themselves: DeepSeek's API is only compatible with the OpenAI /v1/chat/completions endpoint, not the legacy /v1/completions endpoint.
2. Reporter fixed it by adding "useLegacyCompletionsEndpoint": false to the Continue config. Collaborator DillionApple confirmed: 'Currently, we do not supply the /v1/completions API.'

When to use

You are seeing this: Issue deepseek-ai/awesome-deepseek-integration#11 (closed, 9 comments): VS Code Continue extension hit a 404 against the DeepSeek API. Use this skill when you run into "VS code Continue extension config issue".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The reporter found the cause themselves: DeepSeek's API is only compatible with the OpenAI /v1/chat/completions endpoint, not the legacy /v1/completions endpoint.

Asked in gh:deepseek-ai/awesome-deepseek-integration#11 (https://github.com/deepseek-ai/awesome-deepseek-integration/issues/11): VS code Continue extension config issue.. The issue report: Issue deepseek-ai/awesome-deepseek-integration#11 (closed, 9 comments): VS Code Continue extension hit a 404 against the DeepSeek API. The reporter found the cause themselves: DeepSeek's API is only compatible with the OpenAI /v1/chat/completions endpoint, not the legacy /v1/completions endpoint. The verified answer: Reporter fixed it by adding "useLegacyCompletionsEndpoint": false to the Continue config. Collaborator DillionApple confirmed: 'Currently, we do not supply the /v1/completions API.' Lesson: DeepSeek does not support the legacy completions endpoint; always point OpenAI-compat tools at /v1/chat/completions.