{"version":"2.1.285","anchor":"bash-monitor-clearer-error-when-the-call-was-interrupted","canonical_anchor":"bash-monitor-clearer-error-when-the-call-was-interrupted","heading":"Clearer error when starting a monitor is interrupted","tier":"notice","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/bash-monitor-clearer-error-when-the-call-was-interrupted","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Clearer error when starting a monitor is interrupted\n\nIf starting a monitor is interrupted, Claude Code now cleans up and says the call was interrupted and nothing is running\n\n**What**\n\nWhen Claude starts a monitor and that step is cut short, Claude Code now waits for it to finish and cleans up. If the agent is stopping, it reports the existing stopped error. Otherwise it reports a new message: \"This call was interrupted before the monitor started; nothing is running.\"\n\n**Why**\n\nThe failure message is clearer, and a half-started monitor is not left behind.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}