{"version":"2.1.323","anchor":"session-fork-copies-data-flow-records","canonical_anchor":"session-fork-copies-data-flow-records","heading":"Forked sessions carry over their data-flow records","tier":"internal","area":"Data Flow","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/session-fork-copies-data-flow-records","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Forked sessions carry over their data-flow records\n\nForking a session now copies its data-flow records into the new copy\n\n**Unclear.** What the data-flow tracking records, and whether it is switched on for anyone, is not known.\n\n**What**\n\nForking a session makes a new copy of a conversation that you can continue separately. When you fork, Claude Code now takes the original session's data-flow records as they stood, including whether tracking was on and whether the records were complete, and writes them into the fork.\n\n**Why**\n\nA forked session keeps the data-flow tracking of the session it came from instead of starting without it.\n\n- Area: Data Flow\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}