{"version":"2.1.309","anchor":"acceptedits-mode-stops-auto-approving-some-touch-commands","canonical_anchor":"acceptedits-mode-stops-auto-approving-some-touch-commands","heading":"Accept-edits mode no longer auto-approves some unusual touch commands","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/acceptedits-mode-stops-auto-approving-some-touch-commands","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Accept-edits mode no longer auto-approves some unusual `touch` commands\n\nIn `acceptEdits` mode, `touch` commands with odd or option-like arguments now go through the normal permission check instead of running unasked\n\n**What**\n\n`acceptEdits` is a permission mode in which Claude Code approves file edits on its own without asking you each time. Some simple file commands, including `touch` (which creates an empty file or updates a file's timestamp), were approved automatically in this mode with no further check.\n\nThat approval is now narrower. `touch` is no longer approved automatically when either of these is true:\n\n- Claude Code's cleaned-up version of the command differs from the command as written, apart from surrounding spaces.\n\n- Any argument does not start with a letter, digit, underscore, `.`, `\/` or `~`, optionally after an opening quote.\n\nSuch commands now go through the normal permission check, which may ask you first.\n\n**Why**\n\nThis makes it harder for a `touch` command carrying option-like arguments or shell tricks to be approved silently in `acceptEdits` mode. Ordinary `touch` commands on plain file names are unaffected.\n\n- Area: Permissions\n- Names: `acceptEdits`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}