v5.11.20 — respondToBashCommands detector
New config detector flags when respondToBashCommands isn't disabled in settings.json. Since Claude Code v2.1.186, that setting makes the model emit a reply after every /command and !bash output — quiet but steady output-token spend. The detector tells you to set it to false.
Detection idea and test cases contributed by @danikdanik (#74) — thank you! Ported into the canonical tree and hardened so the always-show config nudge reliably reaches users (bypasses the per-session noise gate and token floor) and renders cleanly.