{"version":"2.1.224","anchor":"inherited-plugins-no-longer-force-a-lockfile-refresh","canonical_anchor":"inherited-plugins-no-longer-force-a-lockfile-refresh","heading":"Inherited plugins no longer force a lockfile refresh","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/inherited-plugins-no-longer-force-a-lockfile-refresh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Inherited plugins no longer force a lockfile refresh\n\nPlugins inherited from elsewhere no longer force your plugin lockfile to refresh.\n\n**What**\n\nClaude Code now records, for each enabled plugin, whether it came from this session's own config. Lockfile freshness checks only require a matching lock entry for those plugins, so plugins inherited from elsewhere no longer trigger a relock.\n\n**Evidence**\n\n`fromOwnConfig`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}