DeepSeek's official docs now publish a WorkBuddy or CodeBuddy local-model contract with fixed `.codebuddy/models.json` paths, a UTF-8 BOM warning, and a direct V4 Pro or Flash selector flow

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.

Accepted official-source monitoring note

Today's accepted item stays DeepSeek-first and uses a current official DeepSeek documentation page because the official @deepseek_ai X surface still was not safely readable in this run. DeepSeek's English homepage still anchors the official X account through the V4 Preview banner, but the direct timeline did not expose a reliably crawlable current post here, so the publish-safe choice is a first-party docs-backed developer update.

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.

Why this is publishable

This is a current official DeepSeek support page, not a rumor, repost, or inventory claim.

It creates a first-party desktop-agent setup contract instead of asking users to stitch together unrelated OpenAI-compatible snippets.
It documents real support-query details developers actually search for: the config file path, the exact endpoint, the UTF-8 BOM parsing trap, and the selector-refresh behavior after restart.
It gives DeepSeek a stronger desktop-workflow story without making WorkBuddy, CodeBuddy, or any non-stocked model the headline product.
It is not a duplicate of the June 25 Anthropic mapping item because today's story is about local desktop model files, selector visibility, and BOM-safe parsing rather than Claude-name routing behavior.

Why this matters for DeepSeek-first SEO pages

Support pages can now target official DeepSeek WorkBuddy setup instead of generic desktop-agent endpoint advice.
Troubleshooting content can explain why valid JSON still fails when the file encoding or restart order is wrong.
DeepSeek-first buying pages can keep the commercial boundary clear: this is a documentation-backed integration workflow, not a new stocked plan on /pricing.

Rejected candidates today

Official X timeline as the primary source: rejected for this run because the homepage still anchored DeepSeek's X presence, but the direct X surface remained unreadable here.
The official Kilo Code page: official and current, but weaker for the single news slot because it is a lighter /connect plus /models flow without the richer desktop-file and BOM troubleshooting contract.
The official Context Caching guide: official and useful, but stronger as long-tail support content than as the one daily news headline.
The official change log and V4 Preview release note: both official, but older and already reflected in existing migration pages.
Official GitHub, Hugging Face, and status surfaces: checked as backup official sources, but no newer first-party update beat the WorkBuddy or CodeBuddy page for today's publish-safe slot.

Editorial takeaway

The safest official DeepSeek story today is a WorkBuddy or CodeBuddy integration documentation check: DeepSeek's own docs now publish the exact .codebuddy/models.json locations, the desktop-safe endpoint contract, the UTF-8 without BOM requirement, and the restart-first troubleshooting order. That is a stronger current developer signal than recycling an older X anchor we still could not fully verify live.