{"version":"2.1.288","anchor":"startup-prefetch-change-around-tengu-cicada-nap-ms","canonical_anchor":"startup-prefetch-change-around-tengu-cicada-nap-ms","heading":"Background loading at startup works slightly differently","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/startup-prefetch-change-around-tengu-cicada-nap-ms","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Background loading at startup works slightly differently\n\nClaude Code changed how it decides on and runs the background loading it does when it starts\n\n**Unclear.** What the new step and the wrapper actually do is not clear.\n\n**What**\n\nClaude Code changed how it handles the work it loads in the background when it starts up. An extra step now runs just before it decides whether to do that loading, and the loading itself is now wrapped in another step. The delay setting that can slow this loading still falls back to 0, meaning no delay, when nothing is sent from the server.\n\n**Why**\n\nThis may change what Claude Code does in the background as it starts.\n\n- Flag `tengu_cicada_nap_ms`: Not enough to say (read for one account on one subscription tier against v2.1.288; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}