Cloud
Cloud for teams
Org catalogs, CLI auth, and immutable published plugin versions.
HarnessTap Cloud is the shared catalog where teams publish and consume plugin versions. The CLI (and Desktop) own local resources, composition, environments, and apply. Cloud is the source of truth for published releases — not for your machine library at ~/.harnesstap.
Where to start
| Your situation | Start here |
|---|---|
New account, first org, first auth login | Getting started |
| Switch orgs, invitations, domain auto-join | Organizations |
| Version history, yank, visibility | Published plugins |
| Roles, shares, org audit log | Access |
| Terminal: login, search, pull, publish | CLI catalog commands |
What Cloud is
- Auth — device-code login from the CLI (
ht auth login); session in the web app - Organizations — tenant boundary for catalogs, members, and billing
- Immutable versions — every
plugin publishappends a version; yank withdraws without deleting history
Cloud does not ship apm-policy.yml. CLI ht audit is the Use-ramp scanner (hidden Unicode, lockfile SHA-256, and optional apm-policy.yml), not a Cloud policy engine. Org-level access is roles, plugin visibility, and the Cloud audit log — see Access.
Typical CLI loop
ht auth login
ht auth status
ht auth orgs --switch org-slug
ht plugin list --search react --remote-only
ht apply org/catalog/plugin-name --project .
ht plugin publish local-pluginPublic catalog baselines (ht apply engineering-foundation) work without login. Private org catalogs require auth.