{"version":"2.1.268","anchor":"bash-monitor-timeout-message-now-reports-event-count-and-dis","canonical_anchor":"bash-monitor-timeout-message-now-reports-event-count-and-dis","heading":"Bash monitor timeout message now reports event count and distinguishes flush\/bounded behaviour","tier":"notice","area":"Monitor Tool","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/bash-monitor-timeout-message-now-reports-event-count-and-dis","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Bash monitor timeout message now reports event count and distinguishes flush\/bounded behaviour\n\nBash monitor timeout messages now report how many events fired instead of a generic message\n\n**What**\n\nWhen a background monitor watching a running bash command times out, Claude Code used to show a flat \"[Monitor timed out \u2014 re-arm if needed.]\" message. Now the message reports how much time passed and how many events the monitor actually delivered before it expired, or says plainly that no events were delivered. Monitors also gained a way to flush pending events and count how many have fired, plus a \"bounded\"\/\"quiet\" mode that can flush accumulated output right before the timeout fires instead of just cutting off.\n\n**Why**\n\nThis gives a clearer picture of whether a monitor missed activity or simply saw nothing happen, making it easier to decide whether to re-arm the watch or move on.\n\n- Area: Monitor Tool\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}