{"version":"2.1.319","anchor":"sparse-checkout-worktree-creation-gated-on-tengu-vast-muffin","canonical_anchor":"sparse-checkout-worktree-creation-gated-on-tengu-vast-muffin","heading":"Sparse worktrees can be set up through a temporary copy to block tampering","tier":"internal","area":"Worktrees","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/sparse-checkout-worktree-creation-gated-on-tengu-vast-muffin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Sparse worktrees can be set up through a temporary copy to block tampering\n\nBehind a switch, creating a sparse worktree checks its folders and prepares files in a temporary git setup before installing them\n\n**Unclear.** Whether the new sparse worktree setup is switched on by default is not known.\n\n**What**\n\nA 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:\n\n- It first checks the new worktree's folder and its git folder.\n\n- It prepares the files using a temporary stand-in git folder instead of running a plain checkout inside the worktree.\n\n- It then moves the results into place.\n\nThis 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\".\n\n**Why**\n\nIt 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.\n\n- Area: Worktrees\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}