Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.290 ·

BYOC runner recovers from stale worktree records and cleans up more safely

The BYOC runner now clears git's stale record of a missing worktree and retries, and deletes worktrees through a helper limited to a trusted folder

You'll notice Improvements
JSON All of v2.1.290
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.290,
ImprovementsSection of the release

Unclear Whether any of this applies outside the BYOC runner is not settled.

What

A worktree is a second working copy of a git repository, kept in its own folder so work can happen there without touching your main checkout. The BYOC runner changes how it handles worktrees in two ways:

  • Creating a worktree: if git refuses because the worktree "is a missing but already registered worktree", meaning git still has a record of it but the folder is gone, Claude Code now drops that old record and tries again.
  • Removing a worktree: Claude Code now uses a helper that only deletes inside a trusted root folder. It no longer deletes the folder with rm -rf and then runs git worktree remove --force.
Why

Runs could get stuck when worktrees lived on network file systems (NFS) or storage mounted into containers (CSI mounts). Clearing the stale record and changing how removal works lets those runs continue.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether any of this applies outside the BYOC runner is not settled.

See this entry in the whole of v2.1.290 →

Feedback