{"version":"2.1.319","anchor":"daemoncoldstart-default-now-fixed-to-transient","canonical_anchor":"daemoncoldstart-default-now-fixed-to-transient","heading":"Background service startup defaults to transient when unset","tier":"use","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/daemoncoldstart-default-now-fixed-to-transient","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Background service startup defaults to transient when unset\n\nWith no `daemonColdStart` setting, Claude Code now falls back to the fixed value \"transient\"\n\n**Unclear.** What the fallback was in the previous build is not known, so whether the default actually changed is unclear.\n\n**What**\n\nWhen no `daemonColdStart` setting is found, Claude Code now uses the fixed value \"transient\". This setting controls how the daemon (a background service Claude Code can run) starts up from cold. Before, the fallback was worked out at run time.\n\n**Why**\n\nIf you never set `daemonColdStart`, the startup behaviour you get is now always the \"transient\" one.\n\n- Area: Sessions\n- Names: `daemonColdStart`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}