mirror of
https://github.com/deepseek-ai/awesome-deepseek-agent.git
synced 2026-11-05 01:07:37 +00:00
[GH-ISSUE #85] deepseek-v4-pro接入cursor后直接报错,有什么办法解决这个问题啊? #29
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/awesome-deepseek-agent#29
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @BBS2013 on GitHub (May 9, 2026).
Original GitHub issue: https://github.com/deepseek-ai/awesome-deepseek-agent/issues/85
@BBS2013 commented on GitHub (May 9, 2026):
HTTP 400
{"error":{"message":"The
reasoning_contentin the thinking mode must be passed back to the API.","type":"invalid_request_error","param":null,"code":"invalid_request_error"}}@Angela459 commented on GitHub (May 9, 2026):
可以看看这个#61
项目链接在这儿https://github.com/yxlao/deepseek-cursor-proxy
@BenedictKing commented on GitHub (May 29, 2026):
这个错误的根因是 DeepSeek 的 API 要求开启 thinking 模式后,后续请求必须把上一轮的
reasoning_content完整回传,否则返回 400。CCX的 Claude Messages 渠道专门处理了这个问题 —— 支持
reasoning_content↔ Claudethinking内容块的双向转换,确保跨轮次的推理内容正确透传。不过需要注意,Cursor 使用的是 OpenAI Chat Completions 格式,CCX 的
/v1/chat/completions透传端点可以直接对接 Cursor,由 CCX 负责与 DeepSeek 通信。如果 DeepSeek 侧对reasoning_content的处理有兼容性问题,CCX 的协议层可以在转发前做归一化。配置方式:
集成指南:docs/ccx.md