{"version":"2.1.318","anchor":"instruction-files-too-long-message","canonical_anchor":"instruction-files-too-long-message","heading":"New message when all instruction files together are too long","tier":"notice","area":"Instruction Files","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/instruction-files-too-long-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### New message when all instruction files together are too long\n\nIf a session's instruction files are too long together to send whole, Claude Code now says so instead of pointing at a file to read\n\n**What**\n\nWhen text has to be cut short, Claude Code normally tells Claude which file to read the rest from and where to start. Sometimes there is no single file to point to. Then it now says \"This session's instruction files are too long together to send whole.\"\n\n**Why**\n\nIt covers the case where the instruction files are too long only in combination, so there is no one file to read the rest from.\n\n- Area: Instruction Files\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}