{"version":"2.1.292","anchor":"warnings-for-unreadable-instruction-files-now-show-a-reason","canonical_anchor":"warnings-for-unreadable-instruction-files-now-show-a-reason","heading":"Warnings about unreadable instruction files now give a reason and stay short","tier":"notice","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/warnings-for-unreadable-instruction-files-now-show-a-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Warnings about unreadable instruction files now give a reason and stay short\n\nWarnings about instruction files that cannot be read now list each file with its reason and collapse into a 'more' summary when the list is long\n\n**What**\n\nInstruction files are files Claude Code reads to learn how you want it to work. When some of them cannot be read, the warning used to show one line per file with an icon and the file name. It is now a list where each entry shows the file's path, shortened if it is long, together with the reason it could not be read. When many files are affected, the list ends with a summary of how many more there are.\n\nThe same list is used in the warning about instruction files that will slow Claude Code down, which also reports files that are large or too numerous.\n\n**Why**\n\nYou can see why a file was skipped, not just that it was, and the warning no longer runs on for screens when many files are involved.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}