{"version":"2.1.307","anchor":"session-approved-tool-runs-now-report-as-ran-shell-variable","canonical_anchor":"session-approved-tool-runs-now-report-as-ran-shell-variable","heading":"Session-approved tools report as run, and shell checks get stricter","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/session-approved-tool-runs-now-report-as-ran-shell-variable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Session-approved tools report as run, and shell checks get stricter\n\nA tool you approved for the session now reports the same as one that ran, and shell commands' variables and `extglob` are checked more strictly\n\n**What**\n\nTwo changes touch how Claude Code handles permissions and shell commands:\n\n- Session-approved tools: when a tool runs because you allowed it for the rest of the session, it is now reported the same way as a tool that ran, along with what gave the permission.\n\n- Shell variables: Claude Code checks shell commands before running them. Under a certain safety check, it now stops treating some variables as safe, and it also flags the `extglob` shell option.\n\n**Why**\n\nThese change what the permission and shell safety checks allow and what they report. Some commands that used to pass may now be treated with more caution.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}