{"version":"2.1.281","anchor":"any-in-arguments-now-marks-read-only-commands-as-needing","canonical_anchor":"any-in-arguments-now-marks-read-only-commands-as-needing","heading":"Any ~ in arguments now marks read-only commands as needing approval","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/any-in-arguments-now-marks-read-only-commands-as-needing","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Any `~` in arguments now marks read-only commands as needing approval\n\nA read-only command with `~` anywhere in its arguments now always needs your approval\n\n**What**\n\nClaude Code lets some read-only commands, which only look at files, run without asking you first. If any argument of such a command contains `~`, the check now treats the command as risky straight away and asks for your approval. In a shell, `~` usually means your home folder.\n\nThe `help` entry in the list of read-only commands now uses the same check. Commands under it that contain `~` are still caught even though the separate check they used to rely on has been removed.\n\n**Why**\n\nA path containing `~` can point somewhere other than it seems, such as into your home folder. Asking first means Claude cannot look in those places without you seeing it."}