{"version":"2.1.321","anchor":"session-fork-reads-transcript-via-file-handle","canonical_anchor":"session-fork-reads-transcript-via-file-handle","heading":"Branching a conversation reads the saved history differently","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/session-fork-reads-transcript-via-file-handle","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Branching a conversation reads the saved history differently\n\nBranching a session and filtering its history now open the saved conversation file in a different way\n\n**What**\n\nA transcript is the file where Claude Code saves a conversation. When you branch a session, which starts a new conversation from an existing one, Claude Code now opens the transcript with a file handle that is closed automatically when done. A routine that filters conversation history does the same. Before, both read the file as a stream.\n\n**Why**\n\nNo visible difference is described. The change is in how the transcript file is opened and closed.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}