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

Installation

Install uze, set up your agents, and keep it current

One line to install, one to set up an agent, one to open the workspace.
curl -fsSL https://uze.sh/i | sh

x86_64 or aarch64, glibc or musl. The installer verifies the release signature and checksum and installs into $XDG_BIN_HOME, or ~/.local/bin when that is unset (set UZE_BIN_DIR to choose another directory). It needs OpenSSH's ssh-keygen (the openssh-client package) to check the signature.

Set up your agents

uze setup

It finds the coding agents on your machine and offers to install the missing ones through each vendor's official installer. Pick the ones you use.

You can also skip this step. When the workspace opens, it sets up every agent already on your machine that is not set up yet, without asking and without updating it. It asks which to install only when your machine has none.

uze setup list    # what is installed and ready

Some installers put the agent in a directory your current shell does not search yet. uze setup still verifies it there, tells you where it is, and reminds you to open a new shell before running it by name. An agent already installed is updated through its own update command instead.

uze setup never edits your shell's startup file. The shims it creates are for the workspace, which puts them first on PATH in its own panes.

Staying current

Updates come on their own: GitHub is asked for a new release at most once an hour, and an open workspace looks again every quarter of an hour, so a workspace left open for days still hears of one. A release is installed as soon as it is found and the workspace tells you: press ↑ restart at the right end of the bar under the agent area, and the workspace comes back where you left it. uze upgrade installs the latest release right away.

Every release is checked against a signature before it is unpacked. One that fails the check is never installed.

VariableValueEffect
UZE_RELEASE_CHANNELlatest (default)Install a release as soon as a check finds it
stableWait until it has been the latest for a day
UZE_AUTOUPDATEnotifyTell you, without installing
offStop checking. In CI (CI set) this is the default

Only a uze the installer placed updates itself: one from cargo install or a package manager is left to whatever put it there, and uze upgrade says so.

Plugins keep current in the same pass. The workspace fetches your marketplaces when it opens and again each hour, and applies the updates that need nothing from you. An update that would run something new, or change what an approved plugin runs, waits for you: a notice offers Review, which opens the plugin list. Nothing that executes is updated without asking.

Removing uze

uze uninstall shows its plan and changes nothing until you confirm it.

uze uninstall           # remove the program; every plugin it delivered keeps working
uze uninstall --purge   # also take back everything it delivered, and remove ~/.uze

--yes skips the question. Do not delete ~/.uze by hand: your agents read their plugins from it. On Windows, the installer does the same, and takes uze off your Path:

& ([scriptblock]::Create((irm https://uze.sh/i))) -Uninstall -Purge

Leave out -Purge to keep ~\.uze.

A project keeps what it declares. In each one, delete agents.yaml, agents.lock and .worktrees/ if you no longer want them, the plugin folders named <plugin>@<market> under .agents/rules/, and their entries in .agents/rules.json. Nothing was written into AGENTS.md, so there is nothing to take out of it.

The agents themselves stay installed; remove them the way their vendor says.

On this page