openclaw - ✅(Solved) Fix [Feature]: DeepSeek V4 Support [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#71006Fetched 2026-04-24 10:36:46
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
Participants
Timeline (top)
labeled ×1

Please add DeepSeek V4 OpenRouter Support

Root Cause

Please add DeepSeek V4 OpenRouter Support

Fix Action

Fixed

PR fix notes

PR #71068: [codex] Add DeepSeek V4 model names

Description (problem / solution / changelog)

Summary

  • Add the official DeepSeek V4 API model names deepseek-v4-flash and deepseek-v4-pro to the bundled DeepSeek provider catalog and make deepseek/deepseek-v4-flash the onboarding default.
  • Keep deepseek-chat and deepseek-reasoner as legacy compatibility aliases while aligning their thinking controls with DeepSeek's V4 modes.
  • Add a DeepSeek-specific thinking payload wrapper that supports the official V4 model IDs, strips thinking payloads from deepseek-chat, preserves tool choice payloads, and avoids OpenAI reasoning_effort.

Why

DeepSeek is deprecating deepseek-chat and deepseek-reasoner on 2026-07-24. This keeps existing configs working while exposing the current V4 model names requested in #71006.

Validation

  • pnpm test:extension deepseek
  • node scripts/run-vitest.mjs run --config test/vitest/vitest.unit-fast.config.ts src/plugin-sdk/provider-stream.test.ts
  • pnpm test:extensions:package-boundary:compile
  • node scripts/check-src-extension-import-boundary.mjs --json
  • node scripts/check-sdk-package-extension-import-boundary.mjs --json
  • pnpm exec oxfmt --check extensions/deepseek/models.ts extensions/deepseek/index.ts extensions/deepseek/onboard.ts extensions/deepseek/index.test.ts docs/providers/deepseek.md src/plugin-sdk/provider-stream.ts src/plugin-sdk/provider-stream.test.ts
  • git diff --check
  • codex review -c model="gpt-5.4" --base origin/main

AI-Assisted Contribution Notes

  • AI-assisted: yes, implemented with Codex.
  • Testing level: targeted validation for the DeepSeek extension and shared provider-stream hook.
  • Prompt/session context: requested DeepSeek V4 model-name support for #71006, then addressed bot and local Codex review feedback around DeepSeek thinking controls, legacy alias behavior, provider payload coupling, and avoiding unofficial model ID assumptions.
  • Understanding: this changes the bundled DeepSeek model catalog/default/docs and adds a DeepSeek-specific thinking payload wrapper so the official V4 models use DeepSeek thinking.type, deepseek-reasoner stays thinking-on, and deepseek-chat stays non-thinking.
  • Review follow-up: local Codex review reported no discrete regression in this patch, and addressed bot review conversations have been resolved.

Closes #71006

Changed files

  • docs/providers/deepseek.md (modified, +9/-7)
  • extensions/deepseek/index.test.ts (modified, +122/-6)
  • extensions/deepseek/index.ts (modified, +31/-0)
  • extensions/deepseek/models.ts (modified, +52/-15)
  • extensions/deepseek/onboard.ts (modified, +1/-1)
  • src/plugin-sdk/provider-stream.test.ts (modified, +75/-0)
  • src/plugin-sdk/provider-stream.ts (modified, +69/-0)
RAW_BUFFERClick to expand / collapse

Summary

Please add DeepSeek V4 OpenRouter Support

Problem to solve

Newest DeepSeek V4 Support

Proposed solution

DeepSeek V4 Support

Alternatives considered

No response

Impact

DeepSeek V4 Support

Evidence/examples

No response

Additional information

No response

extent analysis

TL;DR

Add DeepSeek V4 OpenRouter Support to the existing system.

Guidance

  • Review the current implementation of DeepSeek support to understand the requirements for V4 OpenRouter integration.
  • Investigate the official DeepSeek V4 documentation for OpenRouter support to determine the necessary changes.
  • Consider creating a new module or updating the existing one to accommodate the V4 OpenRouter support.
  • Evaluate the potential impact on the system's performance and functionality after adding the V4 support.

Notes

The lack of specific details about the current implementation and the proposed solution makes it challenging to provide a more detailed fix.

Recommendation

Apply workaround: Add DeepSeek V4 OpenRouter Support as a new feature, ensuring backward compatibility with existing functionality.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - ✅(Solved) Fix [Feature]: DeepSeek V4 Support [1 pull requests, 1 participants]