{"version":"2.1.281","anchor":"worktree-or-bundle-apply-supports-chained-generations","canonical_anchor":"worktree-or-bundle-apply-supports-chained-generations","heading":"Worktree or bundle apply supports chained generations","tier":"internal","area":"Worktrees","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/worktree-or-bundle-apply-supports-chained-generations","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Worktree or bundle apply supports chained generations\n\nApplying worktree or bundle results now supports chained generations and keeps track of what each one was based on\n\n**Unclear.** The finding does not say what a chained generation is or where a user would see this behaviour.\n\n**What**\n\nA worktree is a separate working copy of your project that work can happen in without touching your main copy. When Claude Code applies a result from a worktree or a bundle, the result now carries `link:true`, and a basis is recomputed when the generation is chained.\n\nA snapshot helper now also copies these fields:\n\n- `chained`\n\n- `unshipped`\n\n- `basedOn`\n\n- `recreatedAfterTurn`\n\n**Why**\n\nIn practice, the apply step now records whether a result follows on from an earlier one and what it was based on, instead of treating every result on its own.\n\n- Area: Worktrees\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}