Console
The Musher Console is your web dashboard for managing bundles, API keys, organization settings, and your publisher profile. It is a management surface, not an authoring surface — you create and publish bundles with the Musher CLI, then use the Console to manage visibility, settings, and credentials.
Where Each Tool Fits
| Surface | Best for |
|---|---|
CLI (musher) | Create, validate, publish, yank, and restore bundle versions |
| Console | Manage bundle settings, visibility, API keys, org settings, publisher profile |
| Hub | Browse and discover public bundles |
| API / SDKs | Automate everything programmatically |
Key Concepts
- Organization
- Your team's account. All resources — bundles, API keys, members — belong to an organization.
- Namespace
- Your organization's unique identifier on the registry (e.g.,
acme/). Every bundle name is prefixed with your namespace. - Publisher
- Your organization's public profile on the Hub. Automatically created during onboarding. Manage it from the Console.
- API Key
- An organization-scoped credential used to authenticate CLI, SDK, and direct API requests. See Authentication for setup.
- Trust Tier
- A badge on your publisher profile (Unverified, Community, or Verified) that helps consumers evaluate bundle provenance. Assigned by Musher. See Publisher Profile for details.
What You Can Do
Managing Bundles
Browse, inspect, and change bundle visibility and settings
API Keys
Create, rotate, and revoke API keys
Publisher Profile
Claim your handle and manage your public Hub identity
Security
Manage signing keys and trust policies
Authentication
Set up credentials for CLI, SDKs, and CI/CD
Discovery & the Hub
Make your bundles publicly discoverable