Error / Message
Large file read gets truncated
Very large files get truncated when read, since the full content would consume an outsized share of the context window on its own.
This is a deliberate tradeoff, not a bug — reading an entire multi-megabyte file in full would crowd out everything else in the conversation for one piece of context.
If the part you need is a specific section, asking Claude to read a narrower range (a line range, or search for a specific function first) gets you the relevant detail without the whole file.
For genuinely large generated files (bundled output, logs), that's usually a sign the file itself isn't the right thing to read directly — a targeted search or grep is more useful than the raw file.
Ask for a specific line range or section instead of the whole fileFrequently asked questions
What does "Large file read gets truncated" mean in Claude Code?
Very large files get truncated when read, since the full content would consume an outsized share of the context window on its own.
How do I fix it?
Try: Ask for a specific line range or section instead of the whole file
Is this something to worry about?
For genuinely large generated files (bundled output, logs), that's usually a sign the file itself isn't the right thing to read directly — a targeted search or grep is more useful than the raw file.
Is this covered in the Claude Code Toolkit?
Yes — Large file read gets truncated and patterns like it are part of the full command, hook, and template pack included with a Claude Code Toolkit subscription.
Want the full command, hook, and template pack?
This is one pattern out of the full Claude Code Toolkit — subscribe for the complete set, plus everything we add going forward.
Subscribe to the toolkit — $79/mo