claude-code - 💡(How to fix) Fix Unrecoverable session state when autonomous image Read fails with API 400 [1 comments, 1 participants]

When Claude autonomously reads an image file (without being asked) and the API returns a 400 "Could not process image" error, the conversation enters an unrecoverable state. Every subsequent user message re-triggers the same 400 error, and the session cannot be rescued regardless of what the user types. 3. The file either does not exist or cannot be processed — API returns: {"type":"error","error":{"type":"invalid_request_error","message":"Could not process image"}} 4. User tries to redirect, ignore, or work around the error (e.g. "move on", "start over", "there is no image, stop erroring") 5. Every user message continues to produce the same 400 API error — session is permanently broken

• If an API error occurs from a tool call, user input should be able to interrupt/recover from it The conversation context is poisoned by the failed tool result. Every subsequent API call includes the broken image data and re-triggers the 400 error. The only recovery is to abandon the session and start a new conversation, losing all in-session context.

TL;DR

Clear the conversation context or reset the session state when a 400 "Could not process image" error occurs to prevent subsequent API calls from re-triggering the error.

Guidance

• Identify the source of the autonomous image file reads and disable or modify this behavior to prevent unwanted API calls.
• Implement error handling to catch and clear the conversation context when a 400 error occurs, allowing the user to recover and continue with text-only interaction.
• Consider adding a timeout or retry mechanism to handle temporary API errors and prevent session poisoning.
• Review the API call parameters to ensure that the broken image data is not being included in subsequent calls.

Example

No code snippet is provided as the issue does not include specific code details.

Notes

The solution may require modifications to the Claude model or the API integration to handle errors and clear conversation context effectively.

Recommendation

Apply a workaround to clear the conversation context or reset the session state when a 400 error occurs, as this is a more feasible and immediate solution to prevent session poisoning and allow user recovery.