You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
PluginsArea: what it touches
Internal ChangesKind: in v2.1.280,
ImprovementsSection of the release
What
The SearchPlugins tool got a real description: it now searches your organization's claude.ai plugin catalog proactively, without you needing to name a plugin, whenever a task depends on your team's own process, systems, or data (examples: "ship this to staging", "review this contract against our playbook", "which deals close this week?"). It stays silent if nothing relevant turns up, and won't search again for one-off questions or after you've ignored a previous suggestion.
When results are relevant, Claude calls SuggestPluginInstall to show an install card; otherwise it relays results in plain text.
The SuggestPluginInstall card now records a trigger field marking whether the suggestion was proactive or user_asked, and Claude is now told to keep working on the task after showing the card instead of stopping.
This trigger value is threaded through the system: a related tool's input schema (which dropped a strict enum in favor of looser validation), the plugin listing summary, and the plugin_suggest telemetry event, so the origin of every suggestion is recorded end to end.
Why
Together these changes let Claude Code recommend org-specific plugins on its own initiative when they'd help with a task, rather than only when explicitly asked, while keeping a record of whether each suggestion was proactive or requested.
