{"version":"2.1.299","anchor":"message-rendering-error-detail-limits-prune-earlier-content","canonical_anchor":"message-rendering-error-detail-limits-prune-earlier-content","heading":"Earlier messages can be trimmed when an error reports a limit","tier":"internal","area":"Context Management","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/message-rendering-error-detail-limits-prune-earlier-content","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Earlier messages can be trimmed when an error reports a limit\n\nWhen an error carries a limit, Claude Code can now remove earlier messages, including attachments, that go past it\n\n**Unclear.** What kind of limit is read from the error and which content gets removed is not known.\n\n**What**\n\nWhen Claude Code prepares the conversation, it now reads a limit from an error's details. It then removes earlier messages that go past that limit. Attachments go through the same step.\n\n**Why**\n\nThis can change what Claude Code sends again after an error about a limit.\n\n- Area: Context Management\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}