{"version":"2.1.273","anchor":"plugin-list-and-skill-list-now-also-degrade-gracefully-on-a","canonical_anchor":"plugin-list-and-skill-list-now-also-degrade-gracefully-on-a","heading":"Plugin-list and skill-list now also degrade gracefully on a 404 not-found error, not just 403\/no_scope","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/plugin-list-and-skill-list-now-also-degrade-gracefully-on-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Plugin-list and skill-list now also degrade gracefully on a 404 not-found error, not just 403\/no_scope\n\nPlugin and skill listing now also degrade to an empty list on a 404 'not found' error, not just permission errors\n\n**What**\n\nWhen Claude Code fetches your list of plugins or skills and the request fails, it now falls back to showing an empty list (with a warning logged) instead of throwing an error in one more case: a 404 \"not found\" server response. Previously this graceful fallback only applied to 403 (forbidden) or \"no scope\" permission errors, and skill listing specifically only handled the 403 case. Both plugin and skill listing now share the same check, including the new 404 case.\n\n**Why**\n\nThis prevents a 404 from a plugin or skill listing request from surfacing as a hard error, keeping Claude Code usable even when that endpoint can't find anything to return.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}