Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.280 ·

Claude Code can now proactively search your organization's plugin catalog

Claude Code can now proactively search your org's plugin catalog and suggests installs, tracking why each suggestion fired

Group of 7 You'll notice Internal Changes
JSON All of v2.1.280
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.280,
ImprovementsSection of the release

Unclear The finding shows the new fields exist but not what setting them actually does.

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.

Read from
Names in the bundlesingle_pagetrigger
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since A small documentation edit on prompting-claude-fable-5 touched a line naming trigger after this was published. * **Don't instruct Claude to reproduce its reasoning in the response.** Prompts, skills, or harness instructions that tell the model to echo, transcribe, or explain its internal reasoning as response text can trigger the [`reasoning_extrac… build-with-claude/prompt-engineering/prompting-claude-fable-5 see the edit
Confirmed since Anthropic's documentation has since written up trigger, on context-editing. trigger: build-with-claude/context-editing see the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding shows the new fields exist but not what setting them actually does.
Anthropic's documentation agreesAnthropic's documentation has since written up trigger, on context-editing.

See this entry in the whole of v2.1.280 →

Feedback