{"version":"2.1.269","anchor":"initialworkerstatus-replaces-hardcoded-idle-default","canonical_anchor":"initialworkerstatus-replaces-hardcoded-idle-default","heading":"initialWorkerStatus replaces hardcoded idle default","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/initialworkerstatus-replaces-hardcoded-idle-default","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### initialWorkerStatus replaces hardcoded idle default\n\nWorker status now starts from a configurable initialWorkerStatus instead of always defaulting to idle\n\n**Unclear.** What passes this option in practice, and what other status values are used, is not stated.\n\n**What**\n\nWorker status reporting in Claude Code's connection\/transport layer now starts from a new `initialWorkerStatus` value that can be passed in as an option, instead of always beginning at `\"idle\"` as before.\n\n**Why**\n\nThis lets whatever sets up a worker connection choose its starting status rather than being locked to idle, which is useful if a worker needs to report as already busy or in some other state as soon as it connects.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}