{"version":"2.1.323","anchor":"transcript-loader-handles-voice-call-talk-data-flow-and-der","canonical_anchor":"transcript-loader-handles-voice-call-talk-data-flow-and-der","heading":"Session records now keep track of where a session came from","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/transcript-loader-handles-voice-call-talk-data-flow-and-der","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Session records now keep track of where a session came from\n\nSaved session records can now hold links to the session they came from, and damaged voice call lines are kept with a warning\n\n**What**\n\nClaude Code keeps a transcript, a saved record of each session, on disk. When it reads one back, it now understands a few new kinds of entries:\n\n- Records of how data moved through the session, including a mark for records that are incomplete\n\n- Links saying which session this one was derived from\n\n- Lines of talk from a voice call\n\nIf a line from a voice call is damaged, Claude Code warns once and keeps it as a system line. Resuming a session moved over from somewhere else (teleport) now records a link to the session it came from.\n\n**Why**\n\nThis prepares session records to show where their content came from.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}