DeepSeek Adds WorkBuddy and CodeBuddy Model Configuration

Migrated with permission from DeepSeek V4 Pro, a related editorial property operated by our team.

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.json path and a project-level <your-project>\.codebuddy\models.json path.

DeepSeek gives a concrete endpoint contract for both V4 models: https://api.deepseek.com/v1/chat/completions with deepseek-v4-pro and deepseek-v4-flash exposed through the local model list.

The docs also add a surprisingly specific failure guard: save models.json as 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 curl call before assuming the UI or model selector is broken.