Sign in
← AI PulseAug 4, 2026

Wire · news · Multi-source brief

Claude Plugins Update Tracking for CrowdStrike and Community Entries

Anthropic has updated the tracking mechanism for plugins available to extend Claude's capabilities, specifically affecting CrowdStrike entries and a community repository.

By Illumora Editorial

Source · Aug 4, 2026, 10:07 PM · On Illumora · Aug 4, 2026, 10:12 PM

Media from the primary source — shown here so you can stay on Illumora.

Synthesized from multiple allowlisted primaries on the same event. Lanes →

Brief drafted by Illumora’s editorial model from the linked primary source. Ops desk reviews flagged pieces. How we write →

Read the source →Claude Plugins (official marketplace) — Plugins for Claude | Claude by Anthropic
Save

Anthropic has updated the tracking for plugins that extend Claude's functionality. This change pins the bump action for community entry 9247660a to releases-only tracking. Additionally, two CrowdStrike entries now follow published release tags instead of tracking the main HEAD.

Key Points

  • The bump action for community entry 9247660a is now pinned to releases-only tracking.
  • This change utilizes a new optional tracking-config input.
  • Two CrowdStrike entries now follow published release tags.
  • Previously, these CrowdStrike entries tracked the main HEAD.
  • All other entries continue to HEAD-track as before.

Context

According to Anthropic, users can browse and install plugins to extend what Claude can do. These tools are available for Claude Code and Cowork, and users can also submit their own plugins. The recent update modifies how specific plugin entries are tracked within the system.

Why It Matters

This update indicates a refinement in how plugin versions are managed for Claude, particularly for community contributions and specific vendor integrations. Builders and developers relying on these plugins may experience more stable versioning for the affected entries.

What To Do

  • Note that CrowdStrike plugin entries now follow published release tags.
  • Observe that community entry 9247660a is now releases-only tracked.
  • If developing plugins, review the implications of releases-only tracking versus HEAD-tracking.
  • Consider how the tracking-config input might affect future plugin submissions.