Use

Catalog search

Find a plugin in the public or org catalog, then apply it.

Search the catalog, then ht apply by bare name or selector. apply fetches on demand. Use plugin pull when you want the bundle cached locally before working offline.

Public catalog (no login required for public baselines):

ht plugin list --search foundation --remote-only
ht plugin list --search react --remote-only --format json

--search filters by name, description, or tags. --remote-only skips the local library section.

Marketplace catalogs (Claude Code / Cursor plugin marketplaces, not Cloud) use a different command:

ht plugin search [query]

Apply

ht apply engineering-foundation
ht apply org/catalog/plugin-name --project .
ht plugin pull org/catalog/plugin-name[@version]

Bare names resolve against the public HarnessTap Cloud catalog (and connected orgs). Default scope is the project. Pass --global only for machine home. To apply from apm.yml with no selector, see Apply.

plugin pull fails on a local name conflict instead of overwriting. Use --as <name> to import under a different local name.

After apply

ht status .

Commit apm.lock.yaml, apm.yml if you have one, and the harness directories the plugin wrote. See What to commit and the lockfile.

Private org catalogs need Cloud auth first (ht auth login).