{"version":"2.1.323","anchor":"plugin-directory-copies-are-checked-against-their-commit-and","canonical_anchor":"plugin-directory-copies-are-checked-against-their-commit-and","heading":"Downloaded plugin copies are checked against their recorded commit","tier":"internal","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/plugin-directory-copies-are-checked-against-their-commit-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Downloaded plugin copies are checked against their recorded commit\n\nClaude Code can now check a cached plugin folder against its recorded commit, then re-download it or refuse to load it\n\n**What**\n\nSome plugins are installed from a folder inside a git repository or from a web address, and Claude Code keeps a saved copy on your machine. Claude Code now has a check that compares that saved copy against the commit (the exact recorded version) it is meant to match.\n\n- If the copy does not match, Claude Code can download it again and replace the folder.\n\n- If the copy cannot be checked, Claude Code refuses to load the plugin and says its copy could not be checked against its commit.\n\n**Why**\n\nA plugin copy that was altered or has gone out of date can be repaired or refused instead of being loaded as it is.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}