{"version":"2.1.299","anchor":"session-bundle-explains-missing-or-truncated-transcripts","canonical_anchor":"session-bundle-explains-missing-or-truncated-transcripts","heading":"Session bundles now say why a transcript is missing or cut short","tier":"notice","area":"Feedback","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/session-bundle-explains-missing-or-truncated-transcripts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Session bundles now say why a transcript is missing or cut short\n\nWhen a feedback or session bundle lacks the transcript or has only part of it, Claude Code now tells you why\n\n**What**\n\nWhen you send a feedback report or session bundle (a package of information about your session that you share for support), Claude Code now explains when the conversation transcript is not fully included. The transcript is the saved record of everything said and done in the session. There are two messages:\n\n- Too large: the transcript is too big for one archive, so the bundle contains only the start of it.\n\n- Missing: the session has no transcript saved on disk, so the bundle contains the report only.\n\n**Why**\n\nPeople sending reports can now see why the transcript is absent or incomplete, instead of finding out later that it was not all there.\n\n- Area: Feedback\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}