Storing request/response history with image inputs
Avoid storing request/response history on the server when sending images to prevent potential request failures.
Disable storing previous request/response on server.
Storing request/response history on the server when sending images.
Otherwise the request may fail.
Requests involving image inputs may fail if server-side history storage is enabled. To avoid this, disable the storing of previous request and response history on the server.
- Image Understanding ↗xAI · xAI Docs: Guides · May 29, 2026 · paraphrased
First seen on Subvolts May 29, 2026. Updated Sep 11, 2026. Spotted a problem? Tell us.
- Image UnderstandingxAI · xAI Docs: Guides · May 29, 2026
The Playbook: reusable how-tos, prompts, configs and tips pulled out of the news.
- HeuristicUse image URLs for image understanding promptsProvide public internet URLs for images instead of base64 data URLs when sending images to models. · 5 min
- Code snippetResponses API Image Generation Output HandlingDecode base64-encoded images from the Responses API image generation output. · 2 min
- Troubleshooting fixImage Edit Fails to Change Detail: Point to the PartWhen an image edit doesn't work, specify the exact part of the image to change. · 5 min
- HeuristicImage Prompting: Subject First, Then StylePrioritize subject, state, support, and setting before mood, film stock, or things to avoid. · 5 min
- HeuristicChain image edits for iterative refinementLink multiple image editing operations by feeding the output of one edit as the input for the next. · 15 min
- Code snippetBuild real-time speech-to-speech voice agents over WebSocketsDevelop low-latency, real-time voice agents using WebSockets for interactive conversations with tool use. · 10 min
Questions people ask
- Which AI tools does this work with?
- Any current model. It was seen with Grok in the sources.
- Where did this come from?
- xAI (xAI Docs: Guides). Subvolts collected, normalized and credited it; the link above opens the original.

