{"version":"2.1.314","anchor":"remote-worker-init-no-longer-waits-on-slow-state-read-task","canonical_anchor":"remote-worker-init-no-longer-waits-on-slow-state-read-task","heading":"Remote sessions start without waiting on a slow state read, and upload fewer tasks","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/remote-worker-init-no-longer-waits-on-slow-state-read-task","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Remote sessions start without waiting on a slow state read, and upload fewer tasks\n\nRemote session workers stop waiting for stored state once registered, and skip background monitor socket tasks when uploading\n\n**Unclear.** Whether these changes are switched on for every remote session is not clear, as the start-up change sits behind a setting.\n\n**What**\n\nWhen Claude Code runs as a worker for a remote session, it now behaves differently in three ways:\n\n- Start-up stops waiting for its stored state to load once the worker has registered, and records that it did so in a `read_abandoned_at_registration` field.\n\n- Shell task entries can now exist only while live, without being kept.\n\n- Background monitor socket tasks are left out of what the worker uploads.\n\n**Why**\n\nRemote sessions can start faster, and the uploaded task list carries less noise.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}