{"version":"2.1.310","anchor":"shell-parsing-and-diff-tweaks","canonical_anchor":"shell-parsing-and-diff-tweaks","heading":"Small changes to shell command parsing and edit diffs","tier":"notice","area":"Bash","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/shell-parsing-and-diff-tweaks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Small changes to shell command parsing and edit diffs\n\nClaude Code tightens a command-name check, adds a parser option for backslashes in quotes, and converts tabs when building edit diffs\n\n**Unclear.** What difference these changes make to the diffs and permission prompts a reader sees.\n\n**What**\n\nA diff is the view showing what changed in a file. Claude Code made three small changes:\n\n- The check on command names now also rejects names that match an additional set of patterns.\n\n- The shell command parser has a new option about keeping backslashes inside quoted text.\n\n- Diffs for file edits are now built with tab conversion turned on. The old and new file contents no longer go through a separate conversion step first.\n\n**Why**\n\nThese changes may slightly alter how edit diffs look and how shell commands are read for permission checks.\n\n- Area: Bash\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}