{"version":"2.1.186","anchor":"respondtobashcommands-setting","canonical_anchor":"respondtobashcommands-setting","heading":"respondToBashCommands Setting","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.186\/e\/respondtobashcommands-setting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.186","markdown":"### `respondToBashCommands` Setting\n\nA new per-session setting controls whether Claude generates a response after an `!` input-box bash command completes.\n\n**Details**\n\n- Default: `true` \u2014 Claude responds after `!` commands as before.\n- Set to `false` to silently add the command output to the conversation context without triggering a reply. Useful for quiet shell automation where you want to inject output but not spend tokens on a response.\n- Configurable in settings.json under the same schema as other session settings.\n\n**Evidence**\n\nNew Zod field added to settings schema (search for `\"Whether Claude responds after an input-box ! bash command runs. Set to false to add the command output to context without a response.\"`)"}