{"version":"2.1.229","anchor":"plugins-installed-by-running-a-command-refresh-once-per-sess","canonical_anchor":"plugins-installed-by-running-a-command-refresh-once-per-sess","heading":"Plugins installed by running a command refresh once per session","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/plugins-installed-by-running-a-command-refresh-once-per-sess","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Plugins installed by running a command refresh once per session\n\nPlugins built by running a command re-run once per session in the background.\n\n**What**\n\nA plugin whose source is a command to run, rather than a marketplace download, is now re-run once per session in the background so its output is picked up. The background marketplace updater deliberately skips these, and the auto-update notification splits them into their own group alongside updated and blocked plugins.\n\n**Details**\n\n- Subject to the same managed-settings gate as the rest of plugin auto-updating.\n- No marketplace network refresh happens on this path.\n\n**Evidence**\n\n`is installed by running a command, which the background marketplace update never runs; it is re-resolved separately once per session.`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}