{"version":"2.1.274","anchor":"file-chunk-reads-no-longer-split-a-multi-byte-utf-8-characte","canonical_anchor":"file-chunk-reads-no-longer-split-a-multi-byte-utf-8-characte","heading":"File chunk reads no longer split a multi-byte UTF-8 character at the boundary","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/file-chunk-reads-no-longer-split-a-multi-byte-utf-8-characte","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### File chunk reads no longer split a multi-byte UTF-8 character at the boundary\n\nFile chunk reads no longer cut a multi-byte character in half at the boundary\n\n**What**\n\nWhen Claude Code reads a file in chunks (for example, reading just the end of a large file), it now checks up to 3 bytes before a chunk boundary to see whether it would split a multi-byte UTF-8 character (used for non-ASCII text like accented letters, emoji, or non-Latin scripts) in half. If so, the chunk is trimmed to avoid cutting the character apart. It also strips a leftover byte that can result from a byte-order-mark (a marker some files use at the start to indicate text encoding).\n\n**Why**\n\nPreviously, reading a chunk of a file could end mid-character, producing garbled or invalid text in the output. This fix ensures chunked file reads always end on a clean character boundary.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}