{"version":"2.1.309","anchor":"sandboxed-bash-label-no-longer-special-cases-sed-edits","canonical_anchor":"sandboxed-bash-label-no-longer-special-cases-sed-edits","heading":"sed commands are no longer shown as file edits","tier":"notice","area":"Terminal UI","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/sandboxed-bash-label-no-longer-special-cases-sed-edits","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### sed commands are no longer shown as file edits\n\nBash commands that edit files with sed are now labelled Bash, or SandboxedBash when CLAUDE_CODE_BASH_SANDBOX_SHOW_INDICATOR is set and sandboxed\n\n**What**\n\nClaude Code used to show a Bash command that edited a file with `sed`, a command-line tool that changes text in files, under a file-edit style label with an edit preview. It no longer does. The label is now:\n\n- `SandboxedBash` when `CLAUDE_CODE_BASH_SANDBOX_SHOW_INDICATOR` is set and the command runs in the sandbox, a restricted space that limits what a command can touch\n\n- `Bash` otherwise\n\nThe simulated edit data that used to travel with such commands is no longer stripped when commands are checked.\n\n**Why**\n\nThe imitation file-edit preview for `sed` commands is gone, so these commands appear as ordinary Bash commands.\n\n- Area: Terminal UI\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}