You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current main now has explicit upstream auth/status errors, bounded empty-response recovery, account cooldown handling, session reset diagnostics, and npm run doctor. Please retest with current main. If it still returns HTTP 200 with no content, attach the response body, model, stream flag, npm run doctor output with secrets removed, and server log around the request.
Fixed in main (81374ae). There were two causes of an empty answer with HTTP 200:
client.js only understood the old response/content stream format. DeepSeek now sends fragments, so the client printed an empty line. It now parses the current format and reports HTTP errors instead of exiting silently.
The server stripped every emoji (surrogate pair) from answers, so an emoji-only answer became empty. Only invalid lone surrogates are removed now.
npm run doctor also used to report a pass on an expired login ("biz_data": null). It now fails and tells you to run npm run auth.
Verified against live DeepSeek. If you still get empty responses on current main, please reopen with the npm run doctor output (secrets removed) and the server log.
Activity
SliderVM commentedon Jun 10, 2026
It's very strange. Everything is working fine for me.
I would like to get more details.
ForgetMeAI commentedon Jul 13, 2026
Current main now has explicit upstream auth/status errors, bounded empty-response recovery, account cooldown handling, session reset diagnostics, and npm run doctor. Please retest with current main. If it still returns HTTP 200 with no content, attach the response body, model, stream flag, npm run doctor output with secrets removed, and server log around the request.
dekrezz commentedon Sep 21, 2026
hey, i fixed this in my fork: https://github.com/dekrezz/FreeDeepseekAPI
there was an issue where the request could succeed but no response would actually come back. it should be working properly now.
thanks for reporting it.
Merge branch 'claude/keen-carson-bvdzb1': session deltas, unified mod…
ForgetMeAI commentedon Oct 7, 2026
Fixed in
main(81374ae). There were two causes of an empty answer with HTTP 200:client.jsonly understood the oldresponse/contentstream format. DeepSeek now sends fragments, so the client printed an empty line. It now parses the current format and reports HTTP errors instead of exiting silently.npm run doctoralso used to report a pass on an expired login ("biz_data": null). It now fails and tells you to runnpm run auth.Verified against live DeepSeek. If you still get empty responses on current
main, please reopen with thenpm run doctoroutput (secrets removed) and the server log.Generated by Claude Code