Can My Agent Uselookup · compare · cite

Aug 28, 2026 · Catalog foundation is up

Specification feature · interfaces

Plugin vendor extensionsAgent Plugins 1.0

Preserve namespaced host-specific behavior without representing it as portable core support.

Terminology basis: Agent Plugins 1.0. Agent Plugins 1.0

Plugin vendor extensions: 0 supported, 1 partial, 0 unsupported, 30 unreviewed across 31 cataloged products.

Markdown · JSON

Explore this familyMore in Plugin systems6 capabilities

Current evidence by product

Can my agent use Plugin vendor extensions?

Read across for the answer. 1 of 31 current product columns have reviewed evidence; unreviewed does not mean unsupported.

Known issues (0)Report an issue
  • Supported0
  • Partial1
  • Unsupported0
  • Unknown30
  • Not applicable0

Web

9 products

Desktop

13 products

CLI

9 products

Unknown means no public evidence has been reviewed for that product and capability. It does not mean unsupported.

How statuses are assigned

Definition and scope

What this capability means

Preserve namespaced host-specific behavior without representing it as portable core support.

Support is recorded only when exact, dated evidence covers this behavior.

Traceable compatibility

Assertion ledger

Documentation evidence only. No runtime conformance test is implied.

Claude CLIcli · current
Partial
Target
current Claude Code plugins reference · dated-documentation
Environment
local-default
Observed
2026-08-28
  • vendor-extensionClaude Code supports its own metadata and experimental manifest fields and treats foreign top-level fields as non-fatal, but does not document the Agent Plugins reverse-domain extensions object or namespace-directory model
Evidence
  1. 1. Claude Code keeps foreign manifest fields non-fatal and has native metadata and experimental fields, but does not document the Agent Plugins reverse-domain extensions model.