Unclear It is not stated what the sign-in check looks for, so it is unclear which sign-in states cause a background session to be refused.
The Claude Code daemon is a helper process that keeps running in the background and starts sessions for you, for example scheduled tasks. It has changed in these ways:
- Sign-in check: before the daemon starts most background sessions, it now checks your sign-in and can refuse to start the session.
- Held workers: background workers held back because of sign-in are skipped when the daemon warms up spare workers ahead of time and when it restarts several at once.
ANTHROPIC_PROFILE: sessions the daemon wakes to run a scheduled command no longer receive this variable from the daemon's environment. It normally names which Anthropic profile to sign in with.claude daemon scheduled remove: after printingremoved, the command now runs one more step.- Saving scheduled tasks: if a scheduled task cannot be saved, the command now exits with an error.
These changes stop background workers from running with a sign-in that is out of date or does not match. If background sessions stop starting, check that you are still signed in. Scheduled wake sessions will not pick up the ANTHROPIC_PROFILE value the daemon was started with.
tengu_bg_prewarm_burst_delay_ms Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.323: not a boolean we can read
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
tengu_bg_prewarm_burst_concurrency Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.323: not a boolean we can read
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.323. It isn't a statement about your account. What a flag value here can and cannot tell you
It is not stated what the sign-in check looks for, so it is unclear which sign-in states cause a background session to be refused.