Registry

Musher bundles are distributed as OCI artifacts via bundles.musher.dev. The registry implements the OCI Distribution Spec, so any OCI-compatible client can pull and push bundles.

Authentication

All registry operations require authentication. Use your Musher API key or access token to log in.

bash

mush login

Pulling bundles

Pull a bundle by specifying the namespace, bundle name, and an optional tag. If you omit the tag, latest is used.

bash

mush bundle load acme/code-review:1.0.0

Pushing bundles

Publishing bundles requires the musher CLI and write access to the target namespace. Your organization's namespace is determined during onboarding.

bash

musher push acme/code-review:1.0.0

Listing tags

View all available tags for a bundle:

bash

mush bundle tags acme/code-review

Public vs private bundles

Bundle visibility is configured per bundle in the Console.

Public — anyone with a valid Musher account can pull the bundle. Public bundles are discoverable on the Hub. See Discovery & the Hub for details.
Private — only members of your organization can pull the bundle. Private bundles do not appear on the Hub.