{"version":"2.1.314","anchor":"daemon-start-failure-gives-clearer-message","canonical_anchor":"daemon-start-failure-gives-clearer-message","heading":"Clearer message when a background session fails to start","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/daemon-start-failure-gives-clearer-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Clearer message when a background session fails to start\n\nIf a background session fails to start but nothing was upgraded, Claude Code now suggests `claude daemon stop --any` instead of blaming an upgrade\n\n**What**\n\nClaude Code can run sessions in the background through a helper program called the daemon. When such a session fails to start, Claude Code now checks whether the daemon program is really missing. If it is not, the message now reads: \"Couldn't start the session. Run `claude daemon stop --any`\".\n\nBefore, the message always said the daemon program had been deleted because an upgrade was in progress, and told you to run your command again.\n\n**Why**\n\nThe old message could send you looking for an upgrade that was not happening. The new one gives a command to try.\n\n- Area: Sessions\n- Names: `claude daemon stop --any`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}