Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix DeepSeek Pro model switch fails with generic error in main session [1 comments, 2 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#84035•Fetched 2026-05-20 03:44:57
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
1
Author
Nas20twoNas20two
Participants
clawsweeper[bot]clawsweeper[bot]Nas20twoNas20two
Timeline (top)
labeled ×3closed ×1commented ×1

Error Message

When switching the main session model from Kimi K2.5 to DeepSeek Pro (openrouter/deepseek/deepseek-v4-pro), the system throws a generic error: The error occurs immediately after the model switch when sending a message. The session automatically reverts to Kimi K2.5. 4. Error appears immediately, session reverts to Kimi

Fix Action

Workaround

Use Kimi K2.5 as default model. DeepSeek Flash works for subagents.

RAW_BUFFERClick to expand / collapse

Bug Description

When switching the main session model from Kimi K2.5 to DeepSeek Pro (openrouter/deepseek/deepseek-v4-pro), the system throws a generic error:

"Something went wrong while processing your request. Please try again, or use /new to start a fresh session."

The error occurs immediately after the model switch when sending a message. The session automatically reverts to Kimi K2.5.

Environment

  • OpenClaw Version: 2026.5.12 (f066dd2)
  • OS: macOS (Darwin 25.3.0 arm64)
  • Target Model: openrouter/deepseek/deepseek-v4-pro

Investigation Done

  • ✅ Configuration is correct (model explicitly allowed in config)
  • ✅ OpenRouter status: All operational (99.97% uptime, no incidents in 14 days)
  • ✅ DeepSeek status: No outages reported
  • ✅ Subagents CAN use DeepSeek Pro successfully
  • 🔴 Issue is specific to main session model switch

Likely Cause

Internal OpenClaw gateway/session handoff problem — possibly credential/token not properly passed between providers during model switch.

Workaround

Use Kimi K2.5 as default model. DeepSeek Flash works for subagents.

Steps to Reproduce

  1. Start with Kimi K2.5 as default model
  2. Run: /model openrouter/deepseek/deepseek-v4-pro
  3. Send any message
  4. Error appears immediately, session reverts to Kimi

Reported by: NaSy

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…
#prompt formatting#chain error#conversation history#tool integration#LLM response

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 - 💡(How to fix) Fix DeepSeek Pro model switch fails with generic error in main session [1 comments, 2 participants]