{"version":"2.1.323","anchor":"plugin-install-plugin-not-installed-warning-on-partial-load","canonical_anchor":"plugin-install-plugin-not-installed-warning-on-partial-load","heading":"Plugins not yet installed on a partial load get their own status","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/plugin-install-plugin-not-installed-warning-on-partial-load","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Plugins not yet installed on a partial load get their own status\n\nA plugin missing on a partial load is reported as `plugin-not-installed` with `loadsOnFullLoad`, is not counted as blocking, and is queued for refresh\n\n**What**\n\nClaude Code sometimes loads plugins partially before a full load. When a plugin has no local copy during a partial load, it is now handled differently.\n\n- Status: the loader records a `plugin-not-installed` entry with `loadsOnFullLoad: true`. Before, it recorded a `plugin-cache-miss`.\n\n- Blocking errors: a `plugin-not-installed` entry with `loadsOnFullLoad` set no longer counts as an error that blocks you.\n\n- Refresh: such a plugin is now counted as needing a refresh, in the same way as a cache miss.\n\n**Why**\n\nA plugin that will appear once the full load runs is no longer shown as an error, which should reduce false plugin warnings. It is still picked up and reloaded when needed.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}