{"version":"2.1.296","anchor":"linked-checkout-guard-skipped-when-runsinowndirectories","canonical_anchor":"linked-checkout-guard-skipped-when-runsinowndirectories","heading":"Linked git checkouts without an admin folder are no longer always refused","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/linked-checkout-guard-skipped-when-runsinowndirectories","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Linked git checkouts without an admin folder are no longer always refused\n\nA check that stopped commands in a linked git checkout with no admin folder now lets them through when the environment runs in its own directories\n\n**Unclear.** Which environments are marked as running in their own directories is not stated.\n\n**What**\n\nA linked checkout is an extra working folder attached to a git repository, such as a git worktree. Before, when Claude Code was in a linked checkout that had no admin folder (the folder git uses to keep track of it), a check stopped with exit code 126, the number a program returns to say a command could not run.\n\nThat check now applies only when the environment is not marked as running in its own directories. Where it is, work in the linked checkout goes ahead.\n\n**Why**\n\nIn practice, commands that rely on git can now work in worktree-style environments that this check used to refuse.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}