claude-code - 💡(How to fix) Fix 2000px multi-image limit blocks ALL interaction, not just image reads [1 comments, 2 participants]

When a conversation accumulates multiple PNG images via the Read tool (e.g., visual inspection of code-generated figures), eventually the error appears: This error then blocks ALL further interaction -- not just image reads, but text responses, tool calls, and even processing of user messages. The session becomes completely unresponsive to any input. The only recovery is /compact or /clear. The error should only prevent reading additional images. Text responses, non-image tool calls (Edit, Bash, Grep, etc.), and subagent launches should continue to work. The session should not become completely blocked. 4. The 2000px error blocks everything

TL;DR

The most likely fix is to implement a mechanism to prevent the accumulation of images in the conversation context, such as automatically removing old images when the dimension limit is reached.

Guidance

• Investigate the /compact command to understand how it clears old images from the context and consider integrating this functionality into the main session to prevent image accumulation.
• Modify the error handling to only prevent image reads when the dimension limit is exceeded, rather than blocking all interaction.
• Consider implementing a threshold for the number of images that can be accumulated before triggering the error, to prevent the session from becoming unresponsive.
• Review the Opus 4.6 context usage limits to ensure that the issue is not related to the 1M context limit.

Example

No code snippet is provided as the issue does not contain sufficient technical details to create a specific example.

Notes

The issue may be related to the specific implementation of the Read tool and the conversation context management in Claude Code v2.1.98. Further investigation is needed to determine the root cause of the issue.

Recommendation

Apply a workaround, such as using the /compact command or launching visual inspection in a fresh subagent, until a permanent fix can be implemented. This will allow users to continue working with the tool while preventing the session from becoming unresponsive.