{"version":"2.1.323","anchor":"plugin-install-can-fall-back-to-an-older-version-that-satisf","canonical_anchor":"plugin-install-can-fall-back-to-an-older-version-that-satisf","heading":"Plugin installs fall back to an older version that fits your Claude Code","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/plugin-install-can-fall-back-to-an-older-version-that-satisf","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Plugin installs fall back to an older version that fits your Claude Code\n\nIf a plugin's newest version needs a different Claude Code, installing now tries older marketplace versions that fit instead of failing\n\n**Unclear.** It is not clear under what conditions Claude Code allows the fallback to an older version.\n\n**What**\n\nPlugins add commands, agents and tools to Claude Code. They are installed from a marketplace, a catalogue of plugins. A plugin can state which Claude Code versions it works with in an `engines` field.\n\n- Plugin loading now records the plugin's stated `engines` and checks it.\n\n- If the newest version is rejected because it does not match your Claude Code, Claude Code retries with older versions from the marketplace.\n\n- Each older version that fails is logged as \"was not installed\".\n\n- When an older version is used, the result carries an `olderVersion` field.\n\n- Plugin lookups no longer treat one particular marketplace name specially. Plugins from that marketplace now go through the normal path instead of being turned away. The findings do not show which marketplace this is.\n\n**Why**\n\nInstalling a plugin whose latest release needs a newer Claude Code can now succeed with a compatible older release. Check which version actually installed, because it may not be the latest one.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}