Official2026-06-26
DeepSeek Adds WorkBuddy and CodeBuddy Model Configuration
Checked on June 26, 2026: DeepSeek's official WorkBuddy or CodeBuddy page now documents exact user-level and project-level `models.json` paths, `https://api.deepseek.com/v1/chat/completions` as the endpoint, a UTF-8 without BOM requirement, and a restart-first troubleshooting flow for V4 Pro and V4 Flash.
What we verified on June 26, 2026
- DeepSeek now has an official WorkBuddy or CodeBuddy integration page inside the agent-integrations section of the API docs.
- The page publishes exact local file locations instead of leaving desktop users to guess: a user-level
C:\Users\<your-username>\.codebuddy\models.jsonpath and a project-level<your-project>\.codebuddy\models.jsonpath. - DeepSeek gives a concrete endpoint contract for both V4 models:
https://api.deepseek.com/v1/chat/completionswithdeepseek-v4-proanddeepseek-v4-flashexposed through the local model list. - The docs also add a surprisingly specific failure guard: save
models.jsonas UTF-8 without BOM, because some desktop versions may fail to read local model files when a BOM header is present. - The official troubleshooting order is operationally useful: fully restart WorkBuddy or CodeBuddy, then verify the API key with a direct
curlcall before assuming the UI or model selector is broken.
Sources
- DeepSeek English homepage
- DeepSeek official WorkBuddy or CodeBuddy integration guide
- DeepSeek official Kilo Code integration guide
- DeepSeek official Context Caching guide
- DeepSeek official change log
- DeepSeek official status page
- DeepSeek official GitHub organization
- DeepSeek official Hugging Face organization
- DeepSeek official X account surface