{"version":"2.1.289","anchor":"claude-plugin-eval-resolves-installed-plugins-from-marketpla","canonical_anchor":"claude-plugin-eval-resolves-installed-plugins-from-marketpla","heading":"claude plugin eval tests folder marketplace plugins from where sessions load them","tier":"use","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289\/e\/claude-plugin-eval-resolves-installed-plugins-from-marketpla","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289","markdown":"### `claude plugin eval` tests folder marketplace plugins from where sessions load them\n\nEvaluating an installed plugin from a folder marketplace now runs it from that folder, or stops with an error if the folder no longer lists it\n\n**Unclear.** Whether the same error also appears elsewhere, such as when updating plugins, is not known.\n\n**What**\n\nA marketplace is a catalog of plugins, and some marketplaces are just a folder on your computer. When you run `claude plugin eval` on an installed plugin by name, Claude Code now checks whether its marketplace is a folder:\n\n- If it is, the plugin is evaluated straight from that folder.\n\n- If the folder's catalog cannot be read, or no longer lists the plugin, the command exits with an error starting \"cannot be evaluated where sessions load it\".\n\n- Otherwise it falls back to evaluating a copy.\n\nBefore, the command used only the plugin's recorded install location and refused if that location was unsafe.\n\n**Why**\n\nEvaluating a plugin from a folder marketplace now tests the same files a session would actually load, rather than a copy that may differ.\n\n- Area: Plugins\n- Names: `claude plugin eval`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}