{"version":"2.1.323","anchor":"worktree-kept-base-notice","canonical_anchor":"worktree-kept-base-notice","heading":"A notice now explains when a worktree was kept on its old base","tier":"notice","area":"Worktrees","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/worktree-kept-base-notice","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### A notice now explains when a worktree was kept on its old base\n\nClaude Code now shows a notice when it skipped moving a worktree onto a fresh base\n\n**What**\n\nA worktree is a separate working copy of a git repository that Claude Code can create to work in. Its base is the commit it starts from. When Claude Code skips resetting a worktree onto a fresh base, it now shows a notice saying so.\n\n**Why**\n\nYou can see why a worktree is not on the latest base instead of finding out later.\n\n- Area: Worktrees\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}