Download
Cloud

Connect HarnessTap CLI to HarnessTap Cloud

Authenticate with your cloud account, switch organizations, search and install shared plugin bundles, and publish your own plugins to your team's...

Authenticate with your cloud account, switch organizations, search and install shared plugin bundles, and publish your own plugins to your team's organization. Remote catalog commands live on plugin; use auth for authentication and org context.

Prerequisites

Current HarnessTap CLI installation

Install the latest HarnessTap CLI before connecting it to Cloud.

npx harnesstap@latest init

HarnessTap Cloud account

Sign in with an existing HarnessTap Cloud account or create one before using private org catalogs.

Organization access

Join or create at least one organization so you can search, install, and publish shared plugins beyond the public catalog.

Authenticate and switch organizations

Sign in from the terminal

Start the device flow, sign in with your cloud account, and save a named local account.

harnesstap auth login [account] [--base-url <url>]

Default account name: default. Default base URL: https://harnesstap.com.

Confirm the active identity

Check which user and organization the CLI will use before you install or publish plugins.

harnesstap auth status [--account <name>] [--format human|json]

List and switch organizations

Review the orgs your account can access and switch the active organization for the current account.

harnesstap auth orgs [--account <name>] [--switch <slug>]

Clear a local session

Remove a saved local account when you need to re-authenticate or switch accounts.

harnesstap auth logout [--account <name>]

Cloud accounts are stored in ~/.harnesstap/cloud-accounts.json (or under HARNESSTAP_HOME when set).

Search, install, and publish plugins

Search the cloud catalog

Search the shared plugin catalog in your active cloud organization to find reusable plugins before you install them locally.

harnesstap plugin list --search <query> --remote-only [--account <name>] [--format human|json]

Pull a shared plugin locally

Download a published Agent Plugins package from your organization and import it into the local HarnessTap database under the original or aliased name.

harnesstap plugin pull <org>/<plugin>[@version] [--as <name>] [--account <name>]

plugin pull is distinct from plugin import (local file). plugin pull fails on local name conflict instead of overwriting.

Apply without a prior pull

For public catalog baselines, you can apply by bare name and let the CLI fetch on demand:

harnesstap apply engineering-foundation --project . --harness codex

Use plugin pull when you want the bundle cached locally before working offline.

Publish a local plugin

Export a local plugin as an Agent Plugins package and upload it to your organization's catalog.

harnesstap plugin catalog register <org>/<catalog>
harnesstap plugin publish <plugin> [<org>/<catalog>] [--account <name>]
harnesstap plugin publish plan <plugin>

Publishes to all registered catalogs by default. Pass org/catalog or use plugin catalog bindings to restrict targets.

Suggested team workflow

Stay inside the implemented command set: authenticate, inspect or switch organizations, search plugins, pull or apply shared plugins, and publish local plugins when they are ready for teammates.

1. Authenticate with Cloud

Start the device flow and save an account for the cloud organization you want to use.

harnesstap auth login

2. Inspect your active identity

Check the authenticated user and current organization before you work with shared plugins.

harnesstap auth status

3. Switch organizations when needed

List the organizations your account can reach and switch to the correct one before installing or publishing.

harnesstap auth orgs --switch org-slug

4. Search shared plugins

Browse the plugin catalog for stacks and workflows your team already maintains.

harnesstap plugin list --search react --remote-only

5. Apply or pull a shared plugin

Apply directly by bare name or org/catalog selector, or pull into the local library first.

harnesstap apply org/catalog/plugin-name --project .
harnesstap plugin pull org/plugin-name

6. Publish a local plugin

Share a plugin you maintain back to the active organization so teammates can discover it.

harnesstap plugin publish local-plugin

Troubleshooting

CLI command not found after install

Use npx harnesstap@latest <command> or ensure your global npm bin directory is on PATH.

Authentication fails in headless environment

Use the device-code flow by running harnesstap auth login and following the browser prompt.

Organization not found

Check your active organization with harnesstap auth status and switch using harnesstap auth orgs --switch org-slug.

Plugin install fails with version conflict

Use the --as flag to install the plugin under a different local name to avoid conflicts.

Next steps

Access

Organization roles, published plugin shares, and the Cloud audit log.

HarnessTap Desktop

Local Tauri app with an embedded ht-agent sidecar. Same library as the CLI.

On this page

PrerequisitesCurrent HarnessTap CLI installationHarnessTap Cloud accountOrganization accessAuthenticate and switch organizationsSign in from the terminalConfirm the active identityList and switch organizationsClear a local sessionSearch, install, and publish pluginsSearch the cloud catalogPull a shared plugin locallyApply without a prior pullPublish a local pluginSuggested team workflow1. Authenticate with Cloud2. Inspect your active identity3. Switch organizations when needed4. Search shared plugins5. Apply or pull a shared plugin6. Publish a local pluginTroubleshootingCLI command not found after installAuthentication fails in headless environmentOrganization not foundPlugin install fails with version conflictNext steps