{"version":"2.1.227","anchor":"forked-sessions-inherit-the-parent-s-task-list","canonical_anchor":"forked-sessions-inherit-the-parent-s-task-list","heading":"Forked sessions inherit the parent's task list","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/forked-sessions-inherit-the-parent-s-task-list","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Forked sessions inherit the parent's task list\n\nForking a session now carries the parent's task list over instead of starting empty.\n\n**What**\n\nForking a session now copies the parent's task entries and its high-water mark into the fork, so the new session starts with the same task list instead of an empty one.\n\n**Details**\n\n- each entry is written with an if-absent precondition, so an existing entry in the fork is not overwritten\n- a bounded number of copies run concurrently, and copying stops at a cap with \"[tasks] carry to fork stopped at the cap\"\n- an individual failure logs \"[tasks] carry to fork skipped\" and does not abort the rest\n- runs only on the newer key\/value storage path; when no such backend is attached to the session, the copy is not reached\n\n**Evidence**\n\n`[tasks] carry to fork stopped at the cap`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}