Skip to content
Musher Docs

Managing Bundles

The Console gives you a central view of your organization's bundles. From here you can browse, inspect versions, change settings, and control visibility — all without touching the CLI.

Bundle List

The main bundles page shows every bundle in your organization. Each row displays the bundle name, namespace, visibility badge, latest version number, and last updated time.

Use the controls at the top to narrow the list:

  • Search — filter by bundle name
  • Visibility — show only private or public bundles
  • Source — show bundles created in the Console or pushed via CLI

Bundle Detail Page

Click any bundle to open its detail page. The detail view is organized into tabs:

TabWhat it shows
VersionsAll published versions with their status (published or yanked) and publish date
AssetsThe files included in the bundle — skills, prompts, rules, configs, and more
HubHub listing metadata for public bundles (description, README preview)
SettingsBundle name, description, and visibility controls
READMEThe bundle's rendered README content

Changing Visibility

Open a bundle's Settings tab to toggle between private and public visibility.

  • Private — visible only to members of your organization
  • Public — visible to all Musher users and listed on the Hub

Inspecting Versions

The Versions tab lists every published version of the bundle. Each entry shows the version number, publish date, and current status.

  • Published — active and available for installation
  • Yanked — soft-withdrawn from resolution. New installs won't receive it, but it remains visible for audit purposes.

Click a version to see the specific assets it contains.

Yanking and Restoring Versions

Yanking and restoring versions is done through the CLI. Use musher bundle yank to withdraw a version and musher bundle unyank to restore it. See Publishing Bundles for the full workflow.

Deleting a Bundle

You can delete a bundle from the bundle list or from the bundle's Settings tab. Deleting a bundle removes it and all of its versions from the registry.

What You Can't Do Here

Some operations are CLI-only by design:

  • Publishing new versions — use musher bundle push
  • Editing published version content — published versions are immutable. Publish a new version instead.
  • Creating bundles from scratch — use musher bundle init to scaffold a new bundle locally
  • Yanking or restoring versions — use musher bundle yank and musher bundle unyank

Troubleshooting

IssueCauseFix
Bundle not visible on the HubVisibility is set to privateOpen Settings and switch visibility to public, then create a Hub listing
Bundle visible to some team members but not othersTeam members may not be in the same organizationConfirm all members belong to the organization that owns the namespace