Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.281 ·

Plugin marketplace Ref field accepts branch or tag; SHA is only required for auto_install/required

The plugin marketplace Ref field accepts a branch, tag or commit SHA; a full SHA is only needed for auto_install and required

You'll notice Improvements
JSON All of v2.1.281
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.281,
ImprovementsSection of the release
What

In the plugin marketplace settings form, the Ref field (which picks the version of the marketplace to use) now says it accepts a branch, a tag or a commit SHA. A commit SHA is the long code that identifies one exact saved version in git. The description now states that a full 40-character SHA is only needed for auto_install and required.

Why

For most marketplaces you can enter a branch or tag name, and only need the exact SHA when a plugin is installed automatically or required.

Read from
Names in the bundleauto_installrequired
What the documentation says
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.

Confirmed since Anthropic's documentation has since written up auto_install, on MCP, plugins, skills, and hooks. | `"auto_install"` | Installs automatically on the next sync. Users can uninstall it, and it stays uninstalled for that user. | third-party/claude-desktop/extensions see the edit
Added since A small documentation edit on structured-outputs touched a line naming required after this was published. **Migrating from beta?** The `output_format` parameter has moved to `output_config.format`, and beta headers are no longer required. The `output_format` parameter is deprecated and will be removed in the future. To use it anyway, add the `… build-with-claude/structured-outputs see the edit
Confirmed since Anthropic's documentation has since written up required, on cache-diagnostics. Include the `diagnostics` object on every turn. The object is the opt-in: the API stores a fingerprint only for requests that include it. On the first turn, pass `"previous_message_id": null` to opt in without a prior message to compare ag… build-with-claude/cache-diagnostics see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up required, on cache-diagnostics.

See this entry in the whole of v2.1.281 →

Feedback