{"version":"2.1.248","anchor":"stale-client-data-refetch-timing-moved-to-config","canonical_anchor":"stale-client-data-refetch-timing-moved-to-config","heading":"Stale client-data refetch timing moved to config","tier":"internal","area":"Startup","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/stale-client-data-refetch-timing-moved-to-config","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Stale client-data refetch timing moved to config\n\nHow long startup data stays fresh before refetching now comes from config, not fixed code.\n\n**What**\n\nHow long Claude Code waits before refetching stale startup data, and the jitter around it, now come from configuration rather than fixed values in the code, and both are reported in telemetry.\n\n**Evidence**\n\n`tengu_client_data_stale_refetch`\n\n- Area: Startup\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}