{"version":"2.1.302","anchor":"worktree-session-info-now-records-madeelsewhere","canonical_anchor":"worktree-creation-reports-madeelsewhere-pr-fetch-gate-tengu","heading":"Worktrees now record whether they were made elsewhere","tier":"internal","area":"Worktrees","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/worktree-session-info-now-records-madeelsewhere","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Worktrees now record whether they were made elsewhere\n\nWorktree results and session info gain a `madeElsewhere` field, set to 'enteredByPath' or 'resumedByName' for worktrees Claude Code did not create itself\n\n**What**\n\nA worktree is a second working copy of a git repository in its own folder, which Claude Code can create or switch into. Claude Code now records whether a worktree it is using was made by this process or came from somewhere else, in a new field called `madeElsewhere`.\n\n- The result of creating a worktree now carries `madeElsewhere`. It is false when an existing worktree is refreshed, and is set from a computed value when the worktree already exists.\n\n- The worktree session information now includes `madeElsewhere`, next to the existing `enteredExisting` field.\n\n- A worktree entered by its folder path has `madeElsewhere` set to 'enteredByPath'.\n\n- A worktree reached by resuming a session by name has `madeElsewhere` set to 'resumedByName'.\n\nBefore, only `enteredExisting` was recorded. The check made when fetching a pull or merge request into a worktree, behind `tengu_melodic_octopus`, is not new in this release.\n\n**Why**\n\nClaude Code can now tell a worktree it created itself apart from one that already existed or was reached another way. In practice this affects how such worktrees are tracked during a session.\n\n- Area: Worktrees\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}