Repository navigation
Can't work with deepseek-v4-flash when it opens thinking mode #940
Description
Activity
The error content is
API Error: 400{"error":{"message":"TIreasoning_content' in the thinkingmode mustbeepassed back to theparam":null,"code":"invalid_request_error"}}API","type":"invalid_request_error"have you tried in the main branch? we have already fixed this
Reacted by ljunzhuang357have you tried in the main branch? we have already fixed this
I installed it a few days ago via npm command line, and the version displayed was v0.7.0. I'm a technical novice and don't know if this counts as the main branch.
have you tried in the main branch? we have already fixed this
Does installing the main branch require downloading the source code archive, extracting it, and then installing? I don't know. Just now, after uninstalling via npm command line, I reinstalled it. I see the version is still v0.7.0, and I'm worried it might encounter the same problem again.
have you tried in the main branch? we have already fixed this
Oh, thank you. I just asked the AI, and it said that what I installed via npm command line is the stable version, not the main branch. It seems I need to uninstall that and then install the main branch to try again.
let us know if you are still encountering this issue
let us know if you are still encountering this issue
I installed the main branch using the installation package method, but I see the version still shows as 0.7.0. Now I will test it to see if the penetration issue will still occur.
let us know if you are still encountering this issue
Initially, I tried installing the main branch using the npm command line, but the installation failed.
Then I downloaded the source code archive, extracted it, and installed from inside. But the version still shows as 0.7.0, and the same error occurred again.
Did I not install the main branch?same here ⎿ API Error: 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"}}
have you tried in the main branch? we have already fixed this
Should I use npm run dev? or something different?
if it is dev, the problem keep happeningFor me only checking out pr #895 and building worked, the later prs showed still an issue.
initially it's ok(first time), however it gives an error when i resume session after exit the opencluade.
API Error: 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"}}Thanks to the developers in the community, the issue where DeepSeek would report an error when enabling thinking mode has been resolved in version V0.8.0.
Reacted by Dolph PrefectMuch appreciated! Thanks a lot!
When the thinking mode of DeepSeek-V4-Flash is enabled, it often tends to encounter errors that lead to conversation termination. Once an error occurs, the conversation becomes essentially unusable — any subsequent messages will trigger errors, forcing a restart of the conversation. However, this issue does not occur when the thinking mode is turned off. The downside of not using thinking mode is that the quality of the generated code is lower.