{"version":"2.1.290","anchor":"read-only-check-for-bashpowershell-now-receives-extra-conte","canonical_anchor":"read-only-check-for-bashpowershell-now-receives-extra-conte","heading":"Automatic approval of read-only commands now looks at more information","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/read-only-check-for-bashpowershell-now-receives-extra-conte","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Automatic approval of read-only commands now looks at more information\n\nThe check that lets read-only commands run without asking now receives extra information besides the command itself\n\n**Unclear.** It is not clear what the extra information is or whether it changes which commands are approved automatically.\n\n**What**\n\nClaude Code can approve some commands automatically when they only read things and change nothing. The tool that runs the command decides whether it counts as read-only. That decision used to look only at the command. It now also receives a second piece of information.\n\n**Why**\n\nWhether a command runs without asking can now depend on more than the command alone.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}