2 people reported
All time, since Oct 23.
Status 413 Payload Too Large
“unexpected status 413 Payload Too Large: Failed to buffer the request body: length limit exceeded, url: https://api.deepseek.com/responses”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/20652/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Requests fail with unexpected status 413 Payload Too Large. Seen in powershell on Windows with the models deepseek-flash and DeepSeek-V4.1-Flash-1017, shown as "unexpected status 413".
Is this your bug?
File my report- Where
- Codex CLI
- Error text
unexpected status 413 Payload Too Large"deepseek API inference URL": "https://api.deepseek.com/responses reachable (HTTP 401)",Pasted in 2 reports"deepseek API route probe": "https://api.deepseek.com/models route exists (HTTP 401)",Pasted in 2 reports- Versions
- 26.1013.4894.0
- Platforms
- Windows
- How bad
- Breaks a normal workflow.
Related: Model at capacity errors
Not quite your bug?
- Console windows pop up20 people
- Workspace missing from routing4 people
- App-server socket unreachable2 people