{"version":"2.1.227","anchor":"transcript-reads-can-go-through-the-storage-backend","canonical_anchor":"transcript-reads-can-go-through-the-storage-backend","heading":"Transcript reads can go through the storage backend","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/transcript-reads-can-go-through-the-storage-backend","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Transcript reads can go through the storage backend\n\nTranscript tails and session lists can be read from the storage backend when one is supplied.\n\n**What**\n\nTranscript tails, recent-session lists, session enumeration and project-directory scans gained a path that reads from the storage backend instead of the filesystem. It is only taken when a backend is supplied; otherwise the existing file reads run unchanged.\n\n**Details**\n\n- Tails are assembled by reading records backwards under a byte budget; recent sessions are listed by walking the transcript namespace with cursors instead of directory reads.\n- Transcripts marked as containing third-party content are still withheld, logged per session.\n\n**Evidence**\n\n`withheld: contains_3p_transcript_markers`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}