{"version":"2.1.305","anchor":"bash-mode-input-can-be-marked-as-pasted-and-checked-against","canonical_anchor":"bash-mode-input-can-be-marked-as-pasted-and-checked-against","heading":"Shell commands sent from elsewhere will not run in the wrong folder","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/bash-mode-input-can-be-marked-as-pasted-and-checked-against","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Shell commands sent from elsewhere will not run in the wrong folder\n\nShell commands sent to a session for one folder are now refused with an error if the session is working in a different folder\n\n**What**\n\nBash mode lets you run a shell command directly from the Claude Code prompt. This now also covers shell commands sent from a remote client or from a queue, not only ones you type.\n\nSuch a command can now say which folder it was meant for. If that folder is not the one Claude Code is currently working in, Claude Code shows an error message and does not run the command. The command's output can also be marked as pasted text, and it is then escaped differently before it reaches the conversation. Command output is also now saved by a different route.\n\n**Why**\n\nIt stops a command sent from another device or a queue from running in a folder it was not meant for.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}