Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.302 ·

Worktrees now record whether they were made elsewhere

Worktree results and session info gain a madeElsewhere field, set to 'enteredByPath' or 'resumedByName' for worktrees Claude Code did not create itself

Group of 3 Under the hood Internal Changes
JSON All of v2.1.302
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
WorktreesArea: what it touches
Internal ChangesKind: in v2.1.302,
Internal ChangesSection of the release

What

A 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.

  • 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.
  • The worktree session information now includes madeElsewhere, next to the existing enteredExisting field.
  • A worktree entered by its folder path has madeElsewhere set to 'enteredByPath'.
  • A worktree reached by resuming a session by name has madeElsewhere set to 'resumedByName'.

Before, 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.

Why

Claude 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.

See this entry in the whole of v2.1.302 →

Feedback