Compatibility with DeepSeek model's design to return reasoning content after tool calls?

Ideas Feature Requests
,
1

DeepSeek V4 was released today, and its coding capabilities seem noteworthy. However, Cursor currently doesn’t support DeepSeek’s thinking model design, which requires returning reasoning_content after multi-turn tool calls. Could compatibility be added?

7 Likes
3

same question

4

Yeah please add support for it, would be lovely

1 Like
5

same request, pls try to add this feature

6

same request

7

same request

8

image
image653×1279 104 KB
Seems like it fails when it does a tool call

1 Like
9

Based on the benchmarks, Kimi K2.6 performs better than Deepseek V4.

10

So what’s the harm in having another model to choose from?

1 Like
11

It takes manpower to do such implementations, tests and optimizations. If I have to choose one model to be added, I am not choosing the worse one.

12

Hi folks, I just worte this compatibility layer: https://github.com/yxlao/deepseek-cursor-proxy

The root cause is that DeepSeek API expects reasoning_content to be passed back when tool call + thinking mode is used.

This shall make Cursor work with deepseek-v4-pro and deepseek-v4-flash. Feedback are welcome!

1 Like
16

same request

17

Request ID: cf87522c-4f2a-4ea8-a65f-89b1835e8b9d
{“error”:“ERROR_PROVIDER_ERROR”,“details”:{“title”:“Provider Error”,“detail”:“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”}}”,“isRetryable”:false,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
Provider Error 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”}}
Cvs: Provider Error 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”}}
at Pf_ (vscode-file://vscode-app/o:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29432:24260)
at Rf_ (vscode-file://vscode-app/o:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29432:23144)
at Uf_ (vscode-file://vscode-app/o:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29433:6490)
at q0h.run (vscode-file://vscode-app/o:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29433:11307)
at async cQi.runAgentLoop (vscode-file://vscode-app/o:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41748:12418)
at async Vnm.streamFromAgentBackend (vscode-file://vscode-app/o:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41816:12344)
at async Vnm.getAgentStreamResponse (vscode-file://vscode-app/o:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41816:19567)
at async lCt.submitChatMaybeAbortCurrent (vscode-file://vscode-app/o:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29548:16906)
at async Object.Va [as onSubmit] (vscode-file://vscode-app/o:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40804:4230)
at async vscode-file://vscode-app/o:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40803:100980

18

(post deleted by author)