{"version":"2.1.302","anchor":"task-polling-can-end-at-first-failed-poll-and-unref-its-time","canonical_anchor":"task-polling-can-end-at-first-failed-poll-and-unref-its-time","heading":"Task status checks can stop at the first failure and let Claude Code exit","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/task-polling-can-end-at-first-failed-poll-and-unref-its-time","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Task status checks can stop at the first failure and let Claude Code exit\n\nRepeated task status checks can now give up after one failure and no longer have to keep Claude Code running while they wait\n\n**What**\n\nClaude Code can check on an MCP task over and over until it finishes, which is called polling. Before, it stopped after a fixed number of failed checks. It now has two new options:\n\n- Stop after the first failed check.\n\n- Wait between checks without keeping Claude Code running.\n\n**Why**\n\nA session can exit without waiting for polling to finish.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}