You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
PermissionsArea: what it touches
New FeaturesKind: in v2.1.238,
What probably matters to youSection of the release
What
The folder-trust screen lists commands the repo's own settings would run to mint HTTP headers, alongside the existing marketplace, OpenTelemetry and proxy helper warnings, so a repo cannot introduce a command that runs on first fetch without appearing in the prompt.
Details
The preview now walks extraKnownMarketplaces including alias keys, and lists URL-source and per-plugin headersHelper entries plus command-source plugin entries, rendered as <key>: <command> → <url> with truncation.
Project and local .mcp.json and settings MCP servers that declare a headersHelper are listed too.
Trust telemetry gained hasRepoHeadersHelpers.
Dependency resolution will not auto-install a plugin whose archive is fetched through an entry headersHelper; that requires an explicit /plugin install.
Plugin autoupdate gained the failure classes entry_helper_disabled_by_policy, entry_helper_remote_policy_unconsented and entry_helper_not_inlined, plus deferred and policy-blocked counters.
Evidence
This folder runs commands to mint HTTP headers (headersHelper), declared in , extraKnownMarketplaces[
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreePlugin marketplaces: headersHelper on a url marketplace or a catalog entry runs a command that mints HTTP headers (e.g. a short-lived token)…
