{"version":"2.1.238","anchor":"refused-git-commands-now-tell-you-what-to-do-about-it","canonical_anchor":"refused-git-commands-now-tell-you-what-to-do-about-it","heading":"Refused git commands now tell you what to do about it","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/refused-git-commands-now-tell-you-what-to-do-about-it","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Refused git commands now tell you what to do about it\n\nBlocked git commands now give a concrete fix: run from this directory, or spell the command out.\n\n**What**\n\nWhen Claude Code blocks a git command it cannot tie to your worktree, the explanation and the fix are separate strings, so the fix is concrete: run it from this directory, or spell the command name out literally instead of using a glob.\n\n**Details**\n\n- The multiple-git case no longer ends with \"; split it into separate commands\" and instead gains a run-from-this-directory instruction, with the actual working directory filled in at runtime.\n- The wrapper-script case lost its trailing \"; run the command directly instead\".\n\n**Evidence**\n\n`Spell the command name out literally and run it from `\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}