Registry

Share and distribute formations like Docker images

The MUXI Registry is a distribution hub for formations. Pull community formations with one command. Publish your own. Version control, rollbacks, and namespaces built in.

When to use the registry:

  • Start from a proven template (muxi pull @muxi/hello-muxi)
  • Share formations with the community
  • Version and roll back formations safely

The Docker Analogy

If you know Docker, you know MUXI:

Docker MUXI
docker pull nginx muxi pull @muxi/hello-muxi
docker push myapp muxi push
Dockerfile formation.afs
Docker Hub MUXI Registry
Images Formations

Formations are portable, versioned, shareable - just like container images.

How It Works

Pull a Formation

muxi pull @acme/research-agent
cd research-agent
muxi secrets setup
muxi dev

That's it. Someone else's formation, running locally in seconds.

Push Your Formation

cd my-formation
muxi push

Now anyone can muxi pull @yourusername/my-formation.

Namespaces

Namespace Who Example
@muxi/* Official formations @muxi/hello-muxi
@username/* Individual developers @alice/support-bot

Your GitHub handle is your registry handle - no separate account needed.

Private registries are planned for future release.

Version Control

Automatic Versioning

Every push increments the version:

muxi push
# Published @alice/my-bot v1.0.0

# Make changes...
muxi push
# Published @alice/my-bot v1.0.1

Pull Specific Versions

muxi pull @muxi/hello-muxi@1.0.0      # Exact version
muxi pull @muxi/hello-muxi@^1.0.0     # Latest 1.x.x
muxi pull @muxi/hello-muxi@latest     # Latest (default)

Instant Rollback

muxi server rollback my-assistant
# Shows available versions, reverts instantly

Visibility controls (public/private formations) and private registries are planned for future releases.

What Gets Published

my-formation/
├── formation.afs      ✓ Published
├── agents/            ✓ Published
├── mcp/               ✓ Published
├── sops/              ✓ Published
├── triggers/          ✓ Published
├── knowledge/         ✓ Published (optional)
├── secrets.enc        ❌ Never (encrypted secrets)
├── .key               ❌ Never (encryption key)
└── secrets            ✓ Published (shows required secrets)

Secrets never leave your machine. Users who pull must provide their own credentials.

Discovery

Browse Online

  • Browse by category (support, research, devops)
  • View documentation and examples
  • Check download stats and ratings

Visit registry.muxi.org

Search from CLI

muxi search "customer support"
NAME                     DESCRIPTION                 DOWNLOADS
@muxi/support-bot        Customer support agent      1,234
@alice/helpdesk          Helpdesk assistant          567

Why This Matters

Without Registry With Registry
Copy files manually muxi pull
No versioning Semantic versions, rollbacks
Scattered documentation Centralized, searchable
Reinvent solutions Pull and customize
Manual distribution One command sharing

The result: formations that spread, not code that rots in private repos.

Quick Start

# Try an official formation
muxi pull @muxi/hello-muxi
cd starter
muxi secrets setup
muxi dev

# Publish your own
cd my-formation
muxi login
muxi push

Learn More

Home Registry Documentation Star on GitHub
Get priority support