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

Delivery

How one plugin reaches four agents, and what keeps that safe

Install a plugin once and each agent gets it in its own format, with nothing to do per agent. This page explains how, and what keeps it safe.

One copy, many deliveries

An installed plugin's files live in one place, ~/.uze/sources. No agent reads it. Everything an agent reads is delivered from there: a build in the agent's own directory of ~/.uze/store, a link, an entry in the agent's config. Deleting a build uninstalls the plugin from that agent; uze doctor reports it, and the plugin's files are still in the sources to build from.

The most native route wins

For every capability and every agent, uze picks the first route that keeps the capability's meaning intact:

  1. Native: the agent's own supported mechanism.
  2. Generated native: a folder uze generates, delivered through that mechanism.
  3. Through uze: an adapter uze owns and regenerates, where the agent has no mechanism of its own (OpenCode's hooks).
  4. Partial: it works with a known difference, and uze says which.
  5. Unsupported: stated, with the reason.

What each agent gets today is the Harness support table, generated from the code.

Nothing is touched blindly

Every file or entry uze delivers is recorded with a receipt. Before it changes or removes anything, uze checks the current state against the receipt. If something drifted, because you edited it by hand, uze stops and reports it instead of overwriting.

This is also what lets uze doctor repair a broken delivery without asking: it only rebuilds what it owns and can prove is safe to rebuild.

Running code is your decision

A plugin can run commands on your machine: its MCP servers and hooks, a skill or agent whose text runs a command when it loads (!`…`) or grants itself tools, and the version check of a program it requires. Before installing, uze lists every one and asks, including what a plugin carries in one agent's own format (.claude-plugin/, .codex-plugin/, .mcp.json, hooks/hooks.json). What you approve is the whole plugin: an update that changes any of its files asks again. This holds for plugins a cloned project's agents.yaml declares too. Where there is nobody to ask, it refuses unless you pass --trust, and an update made in the background waits for you to review it. The whole model is on Security.

Plugins are fetched as untrusted input: without your Git config or credentials leaking into the clone, never running a repository's own hooks, and never following a path outside the plugin.

Machine and project

The store and your agents' setup belong to the machine (~/.uze). What a project declares belongs to the project (agents.yaml, agents.lock, AGENTS.md). A command acts on the project it runs in; -m acts on the machine alone.

On this page