{"version":"2.1.290","anchor":"git-seed-worktree-own-vs-linked-objects-mode-wsl-mount-det","canonical_anchor":"git-seed-worktree-own-vs-linked-objects-mode-wsl-mount-det","heading":"Isolated git copies can now get their own object store","tier":"notice","area":"Worktrees","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/git-seed-worktree-own-vs-linked-objects-mode-wsl-mount-det","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Isolated git copies can now get their own object store\n\nClaude Code can now build an isolated git copy with its own object store instead of always borrowing the original's\n\n**Unclear.** It is not clear when Claude Code chooses own mode.\n\n**What**\n\nWhen Claude Code sets up a separate working copy of a git repository, it can now do it in one of two modes. In linked mode the copy borrows the stored file history of the original repository. In own mode it gets its own store and records what it borrowed. Before, that history was always copied from the original.\n\nThe check for whether a folder sits on a Windows drive mounted inside WSL (Windows Subsystem for Linux) can now answer \"unsure\" as well as yes or no.\n\n**Why**\n\nThis affects how Claude Code builds isolated git copies.\n\n- Area: Worktrees\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}