{"version":"2.1.321","anchor":"bash-edit-diff-reader-gate-gains-a-sandbox-on-result-new-fe","canonical_anchor":"bash-edit-diff-reader-gate-gains-a-sandbox-on-result-new-fe","heading":"Showing file changes from shell commands now stops early when sandboxing is on","tier":"internal","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/bash-edit-diff-reader-gate-gains-a-sandbox-on-result-new-fe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Showing file changes from shell commands now stops early when sandboxing is on\n\nWhen sandboxing is on, Claude Code skips its usual way of showing the file changes a shell command made\n\n**What**\n\nWhen Claude runs a shell command that edits files, Claude Code can show you a diff, a side-by-side view of what changed. A check decides how those changes are read. It now gives a distinct answer when sandboxing is enabled. The sandbox is a protective mode that limits what shell commands can touch. Before, the check only chose between its normal reader and a file-watching fallback.\n\nSeveral new internal feature names were also added to a list in this build.\n\n**Why**\n\nIn practice, the diff display for shell-command edits is skipped while the sandbox is on.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}