{"version":"2.1.310","anchor":"plugin-monitors-restricted-by-source-in-some-modes","canonical_anchor":"plugin-monitors-restricted-by-source-in-some-modes","heading":"Plugin monitors are no longer started for every plugin","tier":"notice","area":"Plugins","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/plugin-monitors-restricted-by-source-in-some-modes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Plugin monitors are no longer started for every plugin\n\nClaude Code now filters which plugins get their monitors started, and in some modes only plugins from a source that passes a check are started\n\n**Unclear.** It is not clear which plugin entries are skipped or which modes apply the source check.\n\n**What**\n\nSome plugins come with monitors, which are background watchers that the plugin asks Claude Code to start. Claude Code used to make one check up front and then start the monitors for every plugin. It now filters the list first:\n\n- Some plugin entries are skipped.\n\n- In certain modes, only plugins whose source passes a check get their monitors started.\n\nIf a monitor fails to start, Claude Code logs a message naming the monitor and the error.\n\n**Why**\n\nA plugin monitor that used to start may now stay off, depending on where the plugin came from and which mode Claude Code is running in.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}