Published plugins
Immutable versions, yank, visibility, and how the CLI selects a catalog plugin.
A published plugin is a versioned Agent Plugins package stored under an organization catalog. Each plugin publish (or migrate export --plugin imported in the web UI) appends an immutable version.
Selectors
| Form | Meaning |
|---|---|
org/plugin@version | Legacy two-segment selector; resolves through the org's default catalog |
org/catalog/plugin@version | Canonical three-segment selector |
The CLI accepts both forms for plugin pull. Prefer three segments.
Immutable versions
Every publish creates a version with a unique identifier, changelog notes, and yank support (withdraw without deleting history). Version history is append-only.
ht plugin publish my-setup
ht plugin pull org/catalog/plugin-name[@version]
ht apply org/catalog/plugin-name --project .Visibility
| Visibility | Who can see it |
|---|---|
| Organization | Members of the owning org only |
| Shared | Owning org plus orgs granted read or fork access via plugin shares |
| Public | Anyone with the link (open catalog) |
Adjust visibility from plugin settings at /catalogs/[catalogSlug]/[pluginSlug].
Web UI
Browse catalogs at /catalogs. Organizations with zero published plugins are sent to /onboarding until the first bundle exists.
Profile-tagged plugins
A profile is a published plugin tagged profile — the same versioned bundle, surfaced as a switchable global preset (profile use). Catalog browse has a Profiles tab that filters tag=profile. profile pull and plugin pull resolve the same catalog entries.