{"version":"2.1.290","anchor":"daemon-spawn-records-who-spawned-it","canonical_anchor":"daemon-spawn-records-who-spawned-it","heading":"Background daemons now record what started them","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/daemon-spawn-records-who-spawned-it","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Background daemons now record what started them\n\nStarting a background daemon now passes who started it with `--spawned-by`, and the daemon can be started without the OAuth token in its environment\n\n**What**\n\nClaude Code can start a background daemon, a helper process that keeps running on its own. When it starts a short-lived one, it can now record what started it and passes that along with a `--spawned-by` flag. That value is also included in the usage report sent when the daemon is installed.\n\nThe daemon can now also be started with the OAuth token (the sign-in credential) removed from its environment variables.\n\n**Why**\n\nThe daemon now carries a record of what started it. Removing the sign-in token from its environment means that process does not have to hold your credential.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}