{"version":"2.0.26","anchor":"plugin-registry-system","canonical_anchor":"plugin-registry-system","heading":"Plugin Registry System","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.0.26\/e\/plugin-registry-system","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.0.26","markdown":"### Plugin Registry System\n\n**What:** A persistent metadata tracking system for installed plugins using `installed_plugins.json`\n\n**How it works:** The system automatically creates and maintains a registry file that tracks each installed plugin's version, installation date, file path, and git commit SHA. On first run after upgrading to v2.0.26, your enabled plugins are automatically migrated from settings to this new registry.\n\n**Details:**\n\n- Registry file location: `~\/.claude\/installed_plugins.json`\n- Tracks installation timestamp, last update time, version, install path, and git commit SHA\n- Schema versioning (currently version 1) allows future format migrations\n- Automatically syncs on startup if registry is missing or outdated\n- Distinguishes between local marketplace plugins and external plugins\n- **Evidence**: New functions `ck2()` at line 445175, `W5A()` at line 445178, `is1()` at line 445223, `pk2()` at line 445255, `ns1()` at line 445260, and 10 additional registry management functions in pretty-v2.0.26.js"}