{"version":"2.1.284","anchor":"extensionsworktreeconfig-refusal-broadened","canonical_anchor":"extensionsworktreeconfig-refusal-broadened","heading":"Remote-session uploads from git worktrees handle per-worktree config differently","tier":"notice","area":"Git","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/extensionsworktreeconfig-refusal-broadened","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Remote-session uploads from git worktrees handle per-worktree config differently\n\nPer-worktree git config now has an 'inert' state with its own error message, and the refuse policy now rejects any worktree config that is present\n\n**Unclear.** It is not clear which worktree configuration states exist besides absent, extension and file, or exactly when this check runs.\n\n**What**\n\nA git worktree is an extra checkout of the same repository in another folder. Such a checkout can have its own settings file, `config.worktree`, which git uses when `extensions.worktreeConfig` is turned on. When Claude Code packages a repository to send to a remote or cloud session, it checks for these settings.\n\n- Detection now has three states: `extension`, `inert` (a `config.worktree` file that contains only harmless keys) and `file`. Before, there was a single yes-or-no check for the `extensions.worktreeConfig` extension.\n\n- If the upload fails at the step that handles the worktree's administrative folder, the inert case now has its own explanation. It says that a per-worktree configuration file (config.worktree) stands in its administrative entry.\n\n- The tamper check for linked worktrees is stricter. When the policy is \"refuse\", any worktree config state other than \"absent\" is treated as tampered. Before, only the \"extension\" state was refused.\n\n- Upload diagnostics also record an `inert_config` worktree check.\n\n**Why**\n\nIf you start remote sessions from a linked worktree, error messages are clearer when a `config.worktree` file gets in the way. More worktree setups may also be rejected as tampered during sync than before.\n\n- Area: Git\n- Names: `extensions.worktreeConfig`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}