openclaw - 💡(How to fix) Fix [Bug]: [Bug]: DeepSeek reasoning models (reasoner/v4-pro) still fail on tool call multi-turn with HTTP 400: reasoning_content not passed back [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#71386Fetched 2026-04-26 05:13:22
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×2closed ×1commented ×1

[Bug]: DeepSeek reasoning models (reasoner/v4-pro) still fail on tool call multi-turn with HTTP 400: reasoning_content not passed back

Root Cause

[Bug]: DeepSeek reasoning models (reasoner/v4-pro) still fail on tool call multi-turn with HTTP 400: reasoning_content not passed back

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

[Bug]: DeepSeek reasoning models (reasoner/v4-pro) still fail on tool call multi-turn with HTTP 400: reasoning_content not passed back

Steps to reproduce

[Bug]: DeepSeek reasoning models (reasoner/v4-pro) still fail on tool call multi-turn with HTTP 400: reasoning_content not passed back

Expected behavior

[Bug]: DeepSeek reasoning models (reasoner/v4-pro) still fail on tool call multi-turn with HTTP 400: reasoning_content not passed back

Actual behavior

[Bug]: DeepSeek reasoning models (reasoner/v4-pro) still fail on tool call multi-turn with HTTP 400: reasoning_content not passed back

OpenClaw version

v2026.4.23

Operating system

Window11

Install method

No response

Model

deepseek reasoner/v4-pro

Provider / routing chain

deepseek/deepseek-v4-pro → DeepSeek API (api.deepseek.com)

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue can likely be resolved by ensuring that the reasoning_content is properly passed back in the HTTP request when using DeepSeek reasoning models with multi-turn tool calls.

Guidance

  • Verify that the reasoning_content is being sent correctly in the initial request to the DeepSeek API.
  • Check the API documentation for DeepSeek to confirm the expected format and requirements for the reasoning_content parameter in multi-turn requests.
  • Review the code handling the multi-turn tool calls to ensure it correctly handles and passes back the reasoning_content.
  • Test the API call with a tool like Postman or cURL to isolate the issue and confirm the reasoning_content is being sent as expected.

Example

No code example can be provided without more context on the implementation.

Notes

The solution may depend on the specific implementation details of the DeepSeek API integration, which are not provided in the issue.

Recommendation

Apply workaround: Modify the code handling multi-turn tool calls to ensure reasoning_content is properly passed back, as this is likely a configuration or implementation issue rather than a version problem.

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…

FAQ

Expected behavior

[Bug]: DeepSeek reasoning models (reasoner/v4-pro) still fail on tool call multi-turn with HTTP 400: reasoning_content not passed back

Still need to ship something?

×6

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

Back to top recommendations

TRENDING