{"version":"2.1.235","anchor":"feedback-uploads-are-trimmed-client-side-to-an-8-mib-budget","canonical_anchor":"feedback-uploads-are-trimmed-client-side-to-an-8-mib-budget","heading":"Feedback uploads are trimmed client-side to an 8 MiB budget","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/feedback-uploads-are-trimmed-client-side-to-an-8-mib-budget","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### Feedback uploads are trimmed client-side to an 8 MiB budget\n\nBug report uploads are now trimmed client-side to stay under an 8 MiB budget\n\nBefore a bug report is submitted, Claude Code measures the payload and, if it exceeds 8388608 bytes (with a 65536-byte safety margin), trims it: oldest transcript messages are dropped first, individually oversized messages are removed, and the raw session log tail is shortened or dropped entirely. A machine-readable note describing what was trimmed is appended to the report description, and if the payload is still over budget afterward, an error-level log is written. The `feedback_draft_submit` failure event also gained a `from_this_session` field.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}