{"version":"2.1.311","anchor":"transcripts-and-forks-now-record-which-tools-were-used-tool","canonical_anchor":"transcripts-and-forks-now-record-which-tools-were-used-tool","heading":"Session transcripts now keep a list of the tools used","tier":"internal","area":"Session Transcripts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/transcripts-and-forks-now-record-which-tools-were-used-tool","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Session transcripts now keep a list of the tools used\n\nSession transcripts store a list of tools used, and that list is copied when you branch a session into a new one\n\n**Unclear.** Whether this list is recorded by default is not known.\n\n**What**\n\nClaude Code saves each session (one conversation) as a transcript. Transcripts now hold an entry listing the tools Claude used, such as running commands or editing files. It is written as messages are added, and again when session details are saved.\n\nWhen you branch a session into a new copy, the list is carried over into the copy. It is also included when a session is restored.\n\n**Why**\n\nThis changes what is stored in saved session files.\n\n- Area: Session Transcripts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}