Beta·every release is a pre-releaseAPIs and harness behavior are still changing·every release until v1 is a pre-release
uzev1.0.0-beta.12
Package manager

Marketplaces

Where plugins come from, how to add private ones, and how to create your own

A marketplace is a Git repository that lists plugins. uze-official is built in; add any other one by where it lives:

uze market add owner/repo                        # GitHub
uze market add gitlab:group/repo                 # another host
uze market add https://git.example.com/team/ai   # any Git URL
uze market add ./my-marketplace                  # a directory on this machine
uze market list            # what is registered
uze market remove <name>   # take it and its plugins off this machine

A marketplace inside a larger repository

The catalogue does not have to sit at the repository's root. Point at the directory holding marketplace.json, or name it after a # for a remote:

uze market add ./monorepo/aikit
uze market add gitlab:team/monorepo#aikit

The repository stays the marketplace's identity, and every plugin is read below that directory, from a mirror, from a linked checkout and from agents.lock alike. market add says which directory it reads and whether installs follow its commits (mirrored) or your working tree (linked).

Private marketplaces

Nothing to configure. Public access is tried first, then your Git credential helper (gh auth setup-git, glab, …), then your SSH keys, and remembers what worked. No token is ever written into a project file.

To use owner/repo for your company's own forge, give it a short name:

uze market host work https://git.example.com
uze market add work:team/plugins

Create your own

Ask any agent, with the uze:author skill:

/uze:author create a marketplace for my team's plugins

It creates the repository, registers it, and links it: while you work on it, installs read your files directly, with nothing to publish. When it is ready, push it and share the address.

On this page