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

Authoring

Write a plugin once and it works in every agent

Ask an agent

The fastest way is to describe what you want, with the uze:author skill:

/uze:author create a plugin with a skill that writes our release notes

The agent picks or creates a marketplace, scaffolds the plugin, checks it, and installs it. Then you iterate on the files, and deliver each change to your agents with uze update <plugin> -m.

What a plugin is

hooks.json
mcp.json
plugin.json

Only plugin.json is required; ship what you need. A rule under rules/ is how a plugin tells the agents of every project that declares it something (Rules). These are open standards (Agent Plugins, Agent Skills, MCP), not a uze format, so a plugin written for uze is a plugin for everyone.

A skill is a folder with a SKILL.md:

---
name: release-notes
description: Write release notes from the commits since the last tag
---

What the agent should do when this skill runs.

Try it and share it

Add the plugin from its marketplace, and deliver each change you make to your agents:

uze add -m my-plugin@my-market   # add it to this machine
uze update my-plugin -m          # after each change

To publish, push the marketplace repository. Anyone can then uze market add it.

A marketplace can also live inside the project itself, versioned with it. To scaffold and check plugins without the skill, see the authoring commands in Agent CLI.

Extensions

A plugin can also add to the workspace: a line in the bar under the agent area, a drawer beside the agent, a block of the sidebar, a full-frame view. Harnesses never see it. Writing an extension says how.

On this page