{"version":"2.1.295","anchor":"monitor-tasks-that-stream-are-excluded-from-a-task-filter","canonical_anchor":"monitor-tasks-that-stream-are-excluded-from-a-task-filter","heading":"Streaming MCP monitor tasks are now skipped by a task check","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/monitor-tasks-that-stream-are-excluded-from-a-task-filter","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Streaming MCP monitor tasks are now skipped by a task check\n\nA task check that already skipped ambient WebSocket monitors now also skips MCP monitor tasks that stream\n\n**Unclear.** Which list, count or behaviour this check controls is not known.\n\n**What**\n\nClaude Code can run monitor tasks, which watch something in the background. One check over tasks already skipped ambient monitors that watch a WebSocket connection. It now also skips monitors that watch an MCP server (a server connecting Claude Code to outside tools) when those monitors stream their output.\n\n**Why**\n\nA streaming MCP monitor is now treated the same way an ambient WebSocket monitor already was.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}