OmniscioGuidesRequest unprocessable by the model
Claude Code: request unprocessable by the model (400)
Last checked against Anthropic's documentation on November 18, 2026. By the Omniscio team. Updated .
What is the exact message?
API Error: 400 Request rejected as unprocessable by the model (too many or oversized images, or unsupported parameters)Anthropic notes the wording is the API's own, so the line can vary beyond this form.
What does it mean?
The API refused the request as one the model cannot process. Its own parenthesis names the usual reasons: too many or oversized images, or parameters the model does not support.
On current versions, Claude Code can remove the oldest images and documents from a refused request and send it again, so the oldest items are dropped rather than the whole turn failing. If the error keeps returning, the refused content is not one it strips; use the steps below.
Why it keeps coming back
- The content is in the conversation history. Every later request re-sends it, so the same refusal arrives again.
- You are on a version before v2.1.290. Those versions did not remove images on this refusal, so a long session with hundreds of them could fail every turn.
- A parameter is the cause. When the message names an unsupported parameter rather than images, removing attachments will not help.
How do I fix it?
- Step back past the turn that added the content. Press Esc twice and continue from before the images or documents went in.
- Or start fresh. Run
/clearfor a conversation that carries none of it. - Paste smaller images. Take a screenshot of the region you need instead of the whole screen, and resize a large image before you attach it.
- Update Claude Code. From v2.1.290 it can remove the oldest images and documents from a refused request and retry, which stops a long session failing on every turn.
How do I know it is fixed?
- The next message gets a reply instead of the 400.
- Pasting a small screenshot into the same session gets a reply instead of the 400.
- Pasting a small screenshot into the same session works, which shows the model is fine with the request shape.
Where these answers come from
- The message, quoted word for word, the image-removal behaviour and the v2.1.290 note: Anthropic's error reference, read November 18, 2026.
- Attachments, the 32MB request limit and the single-image limits, for the boundaries against Request too large and Image was too large: the same reference, read the same day.
Common questions
Is this the same as Request too large?
No. Request too large is the API's 32MB limit on the raw body. This is the model refusing content it cannot process, such as too many or oversized images.
Why does it fail on every turn?
The refused content sits in the conversation history, so every request carries it again. Versions before v2.1.290 did not strip the images on this refusal.
Do I have to start a new conversation?
Not always. Press Esc twice to step back past the turns that added the content, or run /clear if starting fresh is easier.
What if the message names a parameter, not images?
Then removing attachments will not clear it. The parameter reaches the model from outside the conversation; the likely sources are a gateway rewriting the body, or a --settings file or ANTHROPIC_* variable adding it. Find that source and take the parameter out.