{"version":"2.1.309","anchor":"sed-i-treated-as-an-in-place-formatterfixer-command","canonical_anchor":"sed-i-treated-as-an-in-place-formatterfixer-command","heading":"sed -i is now recognised as a command that edits files in place","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/sed-i-treated-as-an-in-place-formatterfixer-command","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### `sed -i` is now recognised as a command that edits files in place\n\nClaude Code now recognises `sed -i` and `gsed -i` as in-place file edits, alongside commands using `--fix`, `--in-place` or `--auto-correct`\n\n**Unclear.** It is not clear what Claude Code does differently with a command once it is recognised as an in-place edit.\n\n**What**\n\nClaude Code keeps a list of patterns for shell commands that change files where they sit (an \"in-place\" edit) rather than printing a result. That list already matched commands using `--fix`, `--in-place` and `--auto-correct`. It now also matches `sed -i` and `gsed -i`, including when `-i` is combined with other short options such as `-Ei`.\n\n**Why**\n\nCommands that Claude Code runs in your terminal are sorted into kinds, and this list marks the ones that act like formatters or fixers. A `sed -i` command now lands in that group instead of being treated as an ordinary command.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}