{"version":"2.1.267","anchor":"new-startup-step-artifact-roster-cache-is-refreshed-and-a","canonical_anchor":"new-startup-step-artifact-roster-cache-is-refreshed-and-a","heading":"New startup step: 'artifact roster' cache is refreshed and awaited during CLI setup","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/new-startup-step-artifact-roster-cache-is-refreshed-and-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### New startup step: 'artifact roster' cache is refreshed and awaited during CLI setup\n\nStartup now refreshes an 'artifact roster' cache and can wait for it before continuing\n\n**What**\n\nClaude Code's startup sequence now conditionally kicks off a refresh of an 'artifact roster' cache early on, based on checks of whether it's needed and whether identity is already known. If that refresh was started, startup later waits for it to finish, up to a timeout, before continuing \u2014 the same pattern already used for refreshing policy limits at startup.\n\n**Why**\n\nThis keeps the artifact roster (Claude Code's record of available artifacts) up to date at the start of a session without indefinitely blocking startup if the refresh is slow, since it only waits up to a capped timeout.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}