{"version":"2.1.269","anchor":"diff-view-for-bashgit-commands-now-shows-a-per-command-file","canonical_anchor":"diff-view-for-bashgit-commands-now-shows-a-per-command-file","heading":"Diff view for bash\/git commands now shows a per-command file diff","tier":"notice","area":"Bash Tool","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/diff-view-for-bashgit-commands-now-shows-a-per-command-file","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Diff view for bash\/git commands now shows a per-command file diff\n\nRunning a bash or git command now shows a per-command file diff summary of what it changed\n\n**What**\n\nAfter Claude Code runs a bash or git command, it can now show a diff view (a summary of what changed) listing files that were created, updated, or deleted, along with per-file line-count changes and the actual changed lines (hunks). If two commands ran in the same repository at the same time, it shows a note explaining that a change made by either one may show up under either result, since it can't always tell which command caused which change. A disclaimer also makes clear this view is a convenience summary of what the command changed, not a review or audit of the command itself.\n\n**Why**\n\nThis makes it easier to see the effect of a command at a glance, without having to run `git diff` yourself, while being explicit that it's not a substitute for actually checking what a command did.\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}