{"version":"2.1.295","anchor":"git-stash-list-marked-respectsdoubledash-false","canonical_anchor":"git-stash-list-marked-respectsdoubledash-false","heading":"git stash list permission check no longer trusts arguments after --","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/git-stash-list-marked-respectsdoubledash-false","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### `git stash list` permission check no longer trusts arguments after `--`\n\nThe read-only rule for `git stash list` no longer assumes everything after `--` on the command line is safe\n\n**Unclear.** It is not clear whether `git stash list` commands with arguments after `--` now ask for your permission where they did not before.\n\n**What**\n\nClaude Code keeps a list of commands it treats as read-only, meaning they only look at things and change nothing. The entry for `git stash list` has been tightened: arguments that come after `--` are no longer assumed to be harmless when Claude Code checks the command.\n\n**Why**\n\nThis makes the permission check stricter. A command that hides extra arguments after `--` is no longer counted as safe just because of where they sit.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}