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

Overview

The package manager for coding agents. Add a plugin to a project once, and every agent receives it

Install a plugin once, and every agent you use gets it: Claude Code, Codex, OpenCode and Antigravity, each in its own format. A plugin bundles skills, MCP servers, agents, hooks and rules.

Your project records its plugins, so whoever clones it gets the same ones. They reach the agents you start yourself, in a terminal, an editor or CI, and the ones the workspace starts. The package manager is a plain CLI and does not need the workspace.

Adding a plugin

uze add <plugin>@<marketplace>  # add it to this project
uze <plugin>@<marketplace>      # the same, without the verb
uze inspect <plugin>            # what it carries, and how each agent receives it
uze remove <plugin>             # take it out of this project

A plugin that runs commands on your machine (an MCP server, a hook, a skill that runs a command when it loads) lists them and asks before installing.

Your project remembers

Adding a plugin writes two files at the project root. Commit them:

  • agents.yaml: the plugins this project wants.
  • agents.lock: the exact version each one resolved to.

Anyone who clones the project gets the same plugins, at the same versions, with uze install, which installs what the project declares and takes no plugin:

git clone …
uze install

Updating

uze update             # every plugin, to the newest version
uze update <plugin>    # just one

uze install never moves a version; uze update does, and rewrites agents.lock.

Each agent receives a plugin through its own native mechanism. How delivery works explains the routes and what keeps them safe.

Only on this machine

To add a plugin for yourself without writing it into the project, add -m:

uze add <plugin>@<marketplace> -m
uze remove <plugin> -m

On this page