{"version":"2.1.321","anchor":"file-read-result-reports-in-working-folder-and-enforces-a-si","canonical_anchor":"file-read-result-reports-in-working-folder-and-enforces-a-si","heading":"A file-reading step now refuses files over a size limit","tier":"internal","area":"Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/file-read-result-reports-in-working-folder-and-enforces-a-si","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### A file-reading step now refuses files over a size limit\n\nOne file-reading step now refuses text over a size limit and reports whether the file is inside the working folder\n\n**Unclear.** It is not clear which feature reads files this way, so a reader cannot tell when the size limit applies to them.\n\n**What**\n\nOne of the ways Claude Code reads a file now stops when the text is larger than a set number of bytes, and reports `over_the_cap` instead of the text. When it does read the file, it now also reports whether the file is inside the working folder (`in_working_folder`). Before, it simply returned the text.\n\n**Why**\n\nThis changes what happens when a large file goes through this path, which seems to be one used for file attachments.\n\n- Area: Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}