{"version":"2.1.289","anchor":"plugin-list-shows-where-each-plugin-was-read-from-and-its-fo","canonical_anchor":"plugin-list-shows-where-each-plugin-was-read-from-and-its-fo","heading":"claude plugin list shows which folder a plugin was read from","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289\/e\/plugin-list-shows-where-each-plugin-was-read-from-and-its-fo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289","markdown":"### `claude plugin list` shows which folder a plugin was read from\n\n`claude plugin list` now shows a \"Read from:\" line and folder version for plugins loaded from a folder, with matching fields in JSON output\n\n**What**\n\nWhen Claude Code loads a plugin from a marketplace that points at a folder on your computer, it now records when it read that folder. `claude plugin list` uses this:\n\n- Text output adds a \"Read from:\" line and shows a version that takes the folder into account.\n\n- JSON output adds `readFromFolder` and `folderVersion` fields.\n\nPlugins without a recorded folder read show only the version and scope, as before.\n\n**Why**\n\nIf you keep a local copy of a plugin, you can now see which copy on disk Claude Code is actually using.\n\n- Area: Plugins\n- Names: `claude plugin list`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}