{"version":"2.1.227","anchor":"auto-mode-can-treat-linked-git-worktrees-as-already-approved","canonical_anchor":"auto-mode-can-treat-linked-git-worktrees-as-already-approved","heading":"Auto mode can treat linked git worktrees as already-approved directories","tier":"soon","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/auto-mode-can-treat-linked-git-worktrees-as-already-approved","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Auto mode can treat linked git worktrees as already-approved directories\n\nAuto mode could stop asking about sibling git worktrees of the same repo, but it is off.\n\n**What**\n\nIn auto permission mode, when a tool is held for approval only because it touches a directory outside the session, Claude can look up the other working trees linked to the same repository and retry the check with those included. The resolver returns nothing unless `tengu_auto_mode_worktree_fast_path` is on, and it falls back to off, so behaviour is unchanged in this build.\n\n**Evidence**\n\n`tengu_auto_mode_worktree_fast_path`\n\n- Flag `tengu_auto_mode_worktree_fast_path`: Not enough to say (read for one account on one subscription tier against v2.1.227; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Permissions\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}