{"version":"2.1.318","anchor":"macos-bash-heredoc-guidance","canonical_anchor":"macos-bash-heredoc-guidance","heading":"On macOS, Claude is told to pass multi-line text on standard input","tier":"notice","area":"Bash Tool","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/macos-bash-heredoc-guidance","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### On macOS, Claude is told to pass multi-line text on standard input\n\nA new note tells Claude that heredocs inside $(...) are unreliable in macOS's bash 3.2 and to pass multi-line text on standard input instead\n\n**What**\n\nThe instructions for Claude's shell tool gain a note for macOS. It says the tool runs macOS's \/bin\/bash version 3.2, where a heredoc (a way of writing several lines of text straight into a command) does not work reliably inside `$(...)`. Claude is told to pass multi-line text on standard input instead.\n\n**Why**\n\nCommands that build multi-line text this way, such as git commit messages, could come out broken on a Mac. Claude should now write them in a way that works there.\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}