Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.319 ·

Sparse worktrees can be set up through a temporary copy to block tampering

Behind a switch, creating a sparse worktree checks its folders and prepares files in a temporary git setup before installing them

Under the hood Internal Changes
JSON All of v2.1.319
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.319,
Internal ChangesSection of the release

Unclear Whether the new sparse worktree setup is switched on by default is not known.

What

A worktree is a separate working copy of your project that Claude can use. A sparse worktree contains only some of the project's files. When the tengu_vast_muffin switch is on, Claude Code creates a sparse worktree differently:

  • It first checks the new worktree's folder and its git folder.
  • It prepares the files using a temporary stand-in git folder instead of running a plain checkout inside the worktree.
  • It then moves the results into place.

This adds new ways for creation to fail, such as "Failed to checkout sparse worktree: the new worktree's directory or its .git file changed while it was being set up".

Why

It guards against a command running in the sandbox, a restricted area for running commands, tampering with .claude/worktrees. It can also make worktree creation stop with one of the new errors.

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 the new sparse worktree setup is switched on by default is not known.

See this entry in the whole of v2.1.319 →

Feedback