{"version":"2.1.321","anchor":"feedback-transcript-share-degrades-through-more-fallback-pay","canonical_anchor":"feedback-transcript-share-degrades-through-more-fallback-pay","heading":"Shared feedback transcripts shrink step by step when too large","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/feedback-transcript-share-degrades-through-more-fallback-pay","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Shared feedback transcripts shrink step by step when too large\n\nWhen a transcript shared with feedback is too large, Claude Code now drops parts in up to eight steps instead of four\n\n**What**\n\nWhen you share a session transcript with feedback and it is too large to upload, Claude Code removes parts of it until it fits. It used to try four fixed versions. It now steps through these, in order:\n\n- complete\n\n- without request details\n\n- without the raw tail of the log\n\n- without subagents (helper agents Claude starts for side tasks)\n\n- transcript only\n\n- newest messages only\n\n- raw tail only\n\n- details about the session only\n\nA shortened upload can be marked as truncated. Claude Code also records which step was used and how large the upload was.\n\n**Why**\n\nFeedback from long sessions is more likely to arrive with part of the transcript instead of failing or arriving empty.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}