{"version":"2.1.283","anchor":"headless-worker-kind-availability-check-generalised","canonical_anchor":"headless-worker-kind-availability-check-generalised","heading":"Background worker types are now allowed or refused one by one","tier":"internal","area":"Background Daemon","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/headless-worker-kind-availability-check-generalised","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Background worker types are now allowed or refused one by one\n\nClaude Code now checks each background worker type separately to decide whether it may start, instead of only allowing heartbeat\n\n**Unclear.** Which worker kinds the new check allows is not known.\n\n**What**\n\nWhen a background worker starts, Claude Code now asks whether that particular kind of worker is available. Before, when a general check failed, only the \"heartbeat\" kind was allowed. A refused worker still reports \"worker kind '\u2026' is not available\", but exits with a different exit code than the fixed code 2 it used before.\n\n**Why**\n\nIndividual worker kinds may now start or be refused in cases where the old rule treated them all alike.\n\n- Area: Background Daemon\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}