Agent worktrees now ignore repo-supplied filter programs, and refuse to build when git config looks risky.
What's wrong with this entry?
Creating or reusing a worktree for an agent now blanks every filter driver the repository config defines, so checking out files cannot run programs the repo supplies. Three situations stop worktree creation instead: git config that cannot be read, a filter whose name contains = or a newline, and a config using a conditional include. This is active in this build with no flag.
- The repository's local and per-worktree config is read with
--includesand-z --list, and for each filter driver found the git call gets-c filter.<name>.clean=,.smudge=,.process=and.required=false. - Each refusal records its own telemetry:
git_worktree_create_config_unreadable,git_worktree_create_filter_name_unrepresentable,git_worktree_create_conditional_include. - A conditional include is refused because the set of filters a checkout would load cannot be worked out ahead of time.
The repository git config has a conditional include (includeIf), so the filter drivers a checkout would load cannot be determined
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.242
Claude checks a checkout's git configuration before running git in it
Both mention safety
-
v2.1.242
Wider detection of tampered git directories
Both mention safety
-
v2.1.242
Claude Code's git commands no longer recurse into submodules
Both mention safety