Deepseek-v4-pro error report

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

deepseek v4 error report

Provider returned error: {“error”:{“message”:“The reasoning_content in the thinking mode must be passed back to the API.”,“type”:“invalid_request_error”,“param”:null,“code”:“invalid_request_error”}} Request ID: b01fb6e9-b07d-4bcb-b438-36c29312af2d

Steps to Reproduce

Using the model: deepseek-v4-pro

Operating System

MacOS

Version Information

Version: 3.2.11
VSCode Version: 1.105.1
Commit: e9ee1339915a927dfb2df4a836dd9c8337e17cc0
Date: 2026-04-24T14:36:47.933Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.4.0

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, this is a known limitation for BYOK with DeepSeek V4 and Kimi in thinking mode. Cursor currently doesn’t pass reasoning_content back in a multi-turn flow with tool calls, so the provider rejects the follow-up request. One tool call usually works, and the second step fails with the same 400.

Megathread on this: Compatibility with DeepSeek model’s design to return reasoning content after tool calls? Compatibility with DeepSeek model's design to return reasoning content after tool calls?
I’ll close your thread as a duplicate so the discussion stays in one place.

We’ve reported the issue internally, but I can’t share an ETA for a fix yet. We’ll post updates in the megathread.