Explicit mode selection
Treat thinking versus non-thinking as a product decision tied to complexity, speed, and token use.
Choose the V4 model and thinking mode explicitly, then preserve reasoning context correctly across tool calls.
The mental model
“Model mode and conversation plumbing matter as much as the words in the prompt.”
Three levels
Do not add production scaffolding before you can describe and measure a good single-task result.
Start with the correct capability and latency profile.
Produce predictable results for automation.
Keep long agent loops valid and coherent.
Starter template
Replace the bracketed text, run it on a real task, and add guidance only when you can name the failure it fixes.
Mode: [thinking for complex reasoning / non-thinking for fast routine work]
Task:
[One concrete outcome]
Available tools:
- [tool name]: [when it should be used]
Output:
- Format: [text or JSON]
- Required fields: [fields]
- Validation: [observable check]
If JSON is required, return JSON matching this example:
{"result":"...","evidence":["..."]}Treat thinking versus non-thinking as a product decision tied to complexity, speed, and token use.
Combine the API response format with the word JSON, a sample object, and adequate output space.
OpenAI-compatible or Anthropic-compatible syntax does not remove DeepSeek-specific conversation requirements.
An integration still calls deepseek-chat or deepseek-reasoner after their July 24, 2026 retirement.
Fix: Migrate to deepseek-v4-pro or deepseek-v4-flash and choose thinking mode explicitly.
A thinking-mode tool loop fails on the next request.
Fix: Preserve the documented reasoning content in conversation history alongside the assistant tool call.
The model returns prose, incomplete JSON, or an empty body.
Fix: Use JSON response format, include a JSON example, size max tokens, validate, and retry the documented edge case.
Current as of July 26, 2026
DeepSeek’s official change log says the legacy deepseek-chat and deepseek-reasoner aliases were discontinued on July 24, 2026. This guide therefore uses the V4 Pro and V4 Flash names and current thinking-mode requirements.
Evidence ledger
Official provider documentation takes priority. Maintainer field notes are useful evidence, but they are labeled separately.
DeepSeek
V4 model names, release timing, alias retirement, and current API migration state.
DeepSeek
V4 Pro versus Flash positioning, context, interfaces, and dual thinking modes.
DeepSeek
JSON response-format requirements, examples, truncation, and empty-content behavior.
DeepSeek
Thinking-mode tools and strict function-schema behavior.
This guide is reviewed at least every 30 days. Automated checks flag unavailable sources and overdue reviews; substantive advice changes require human verification.