Overview

The package manager is the half of uze that gets your tooling into your agents: plugins, and the project instructions in AGENTS.md. It is a plain CLI and does not need the workspace. It serves the agents you start yourself, in a terminal, an editor or CI, and the ones the workspace starts.

A plugin bundles skills, MCP servers, agents and hooks. You install it once; uze delivers it to Claude Code, Codex, OpenCode and Antigravity, each through its own native mechanism. How delivery works explains the routes and what keeps them safe.

Installing a plugin

uze <plugin>@<marketplace>    # add it to this project
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) 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:

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.

Only on this machine

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

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