{"version":"2.1.290","anchor":"shell-command-output-hint-about-git-steps-moving-the-working","canonical_anchor":"shell-command-output-hint-about-git-steps-moving-the-working","heading":"File changes from a git step are no longer presented as Claude's edits","tier":"notice","area":"Terminal UI","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/shell-command-output-hint-about-git-steps-moving-the-working","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### File changes from a `git` step are no longer presented as Claude's edits\n\nClaude Code now notes that a `git` step in a shell command may have changed files, so those changes may not be edits\n\n**Unclear.** Where this note appears is not stated.\n\n**What**\n\nClaude Code now has a note saying that a `git` step in a command can move the working tree, meaning the files in your project folder, so the changes reported may come from that step rather than from edits.\n\n**Why**\n\nFiles that change because, for example, a branch was switched are less likely to be treated as edits Claude made.\n\n- Area: Terminal UI\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}