{"version":"2.1.290","anchor":"daemon-workers-refuse-to-restart-when-session-facts-restored","canonical_anchor":"daemon-workers-refuse-to-restart-when-session-facts-restored","heading":"Background workers can now stop at startup based on saved session details","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/daemon-workers-refuse-to-restart-when-session-facts-restored","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Background workers can now stop at startup based on saved session details\n\nBackground workers reload saved session details first and may stop with a message, and restarted workers get a count of recent stops\n\n**Unclear.** It is not clear what makes a worker stop at startup or what the worker does with the count.\n\n**What**\n\nClaude Code can run background helper processes, called workers, using `--daemon-worker`. A worker used to start every time. It now first reloads saved details about its session. Depending on those details, it can stop before doing anything, showing a message and exiting with a status code.\n\nThe process that restarts workers now also passes each restarted worker a count of how many times in a row it has stopped temporarily.\n\n**Why**\n\nThis changes how background workers behave when they are restarted.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}