claude-code - 💡(How to fix) Fix Read tool: error message should mention offset/limit parameters

When the Read tool hits its 256KB or 25000 token file size limit, the error message says: This doesn't tell the user how to work around it. The offset and limit parameters exist and work perfectly for chunked reads, but nothing in the error points to them. This is the #1 most frequent error pattern in my usage (9 instances in a 100-session sample). It affects anyone working with log files, session data, or large configs. Every hit requires the user to already know the workaround or look it up externally. Append to the error message:

TL;DR

Update the error message to include guidance on using the offset and limit parameters for chunked reads.

Guidance

• Review the current error message handling to determine the best way to append the suggested fix.
• Consider adding a link to documentation or a tutorial on using offset and limit for chunked reads.
• Test the updated error message with various file sizes and chunking scenarios to ensure it provides accurate guidance.
• Evaluate whether additional error messages or documentation updates are needed to address related issues.

Example

# Example of updated error message
error_message = "File content exceeds maximum allowed size. Use the `offset` and `limit` parameters to read a portion of the file. Example: Read(file_path, offset=0, limit=2000)"

Notes

The suggested fix assumes that the offset and limit parameters are already functional and well-documented. However, it's essential to verify that these parameters work as expected and that users can easily find additional information on using them.

Recommendation

Apply the workaround by updating the error message to include guidance on using the offset and limit parameters, as it directly addresses the most frequent error pattern and improves the user experience.