{"version":"2.1.296","anchor":"session-transcript-writer-no-longer-inits-a-session-log","canonical_anchor":"session-transcript-writer-no-longer-inits-a-session-log","heading":"Session transcripts no longer start a separate session log","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/session-transcript-writer-no-longer-inits-a-session-log","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Session transcripts no longer start a separate session log\n\nThe part of Claude Code that writes a session's transcript no longer sets up a separate session log when it starts\n\n**Unclear.** It is not clear what the session log recorded, so whether any log you can see stops being written is unknown.\n\n**What**\n\nA session is one continuous conversation with Claude Code, and its transcript is the saved record of that conversation. The part of Claude Code that writes the transcript used to also set up a separate session log when it started. It no longer does that step.\n\n**Why**\n\nThis removes a hook, a point where another piece of Claude Code was asked to do something whenever a transcript began.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}