{"version":"2.1.319","anchor":"bash-change-summary-classifications-expanded","canonical_anchor":"bash-change-summary-classifications-expanded","heading":"Finer labels for what a shell command may have changed","tier":"internal","area":"Bash","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/bash-change-summary-classifications-expanded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Finer labels for what a shell command may have changed\n\nClaude Code's summary of what a shell command may have changed now separates writes, git records and MCP calls into more detailed labels\n\n**Unclear.** Where this summary is shown to the user is not stated.\n\n**What**\n\nClaude Code keeps a short summary of what a shell command may have changed. Before, the summary had four values: possible writes, running commands only, tests and lints only, or nothing. It now has more detailed values, including:\n\n- the same command may have written files\n\n- another command may have written files\n\n- only git records changed\n\n- only MCP calls were made (MCP is the system that links Claude Code to outside tools)\n\n- only MCP calls and git records\n\n**Why**\n\nThe report of a command's side effects is more precise.\n\n- Area: Bash\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}