{"version":"2.1.224","anchor":"forking-a-session-tells-the-model-the-fork-is-separate","canonical_anchor":"forking-a-session-tells-the-model-the-fork-is-separate","heading":"Forking a session tells the model the fork is separate","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/forking-a-session-tells-the-model-the-fork-is-separate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Forking a session tells the model the fork is separate\n\nAfter forking, Claude is told the fork is a separate session reachable by name.\n\n**What**\n\nAfter forking, Claude is now told that the fork runs as its own session, that its work is invisible to the current conversation, and that it can be reached by name through the session roster. This branch previously attached nothing.\n\n**Details**\n\n- The message is produced only when cross-session messaging applies; otherwise nothing is attached.\n\n**Evidence**\n\n`The fork runs as its own separate session`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}