{"version":"2.1.299","anchor":"git-cloneinitworktree-detection-changed-for-option-skippin","canonical_anchor":"git-cloneinitworktree-detection-changed-for-option-skippin","heading":"Git clone, init and worktree commands are recognised differently","tier":"internal","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/git-cloneinitworktree-detection-changed-for-option-skippin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Git clone, init and worktree commands are recognised differently\n\nClaude Code now reads git commands in their original order when spotting `clone`, `init` or `worktree`, instead of removing options first\n\n**What**\n\nClaude Code looks at git commands to spot when one is a `git clone`, `git init` or `git worktree` command. When scanning the parts of such a command, it now works from each part's original position in the command. Before, it removed the options (the parts starting with a dash) first and then scanned what was left.\n\n**Why**\n\nThis check is part of how Claude Code judges whether a command is safe. Commands with options placed before the subcommand may now be recognised differently than before.\n\n- Area: Git\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}