{"version":"2.1.315","anchor":"slash-command-sedsshpassset-guard-hardening","canonical_anchor":"slash-command-sedsshpassset-guard-hardening","heading":"Safety checks tightened for sed -i , sshpass and set commands","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/slash-command-sedsshpassset-guard-hardening","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Safety checks tightened for `sed -i`, `sshpass` and `set` commands\n\nClaude Code's automatic safety check for shell commands now catches more risky uses of `sed -i` on macOS and BSD, `sshpass` and `set`\n\n**What**\n\nBefore running a shell command without asking you, Claude Code checks that it is safe. In the list below, a computed word is part of a command whose value is only known when the shell runs it, such as a variable. The check now covers:\n\n- `sed -i` on macOS and BSD: these versions read the word after a bare `-i` as the suffix for a backup file, so a computed word there is now flagged\n\n- `sshpass`, a tool that supplies a password and then runs another program: it now has its own check\n\n- `set` followed by a computed word: now refused\n\n**Why**\n\nFewer commands that could do something unexpected are approved automatically.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}