Getting started
Install uze, set up harnesses, and add your first plugin
Getting started
Install
uze is alpha — no packaged release has shipped yet. Building from source is the only way to run uze today; the installer below already exists and will just say so until the first release does.
git clone https://github.com/hiukky/uze.git
cd uze
cargo install --path . --lockedWorks today on anything Rust's stable toolchain targets.
Set up harnesses
uze setup detects the four supported harnesses on your machine and provisions any missing
binaries through each vendor's official installer:
$ uze setup
▸ Provisioning 4 harnesses through official routes…
[1/4] Claude Code: ready (verified)
[2/4] Codex: ready (verified)
[3/4] OpenCode: ready (verified)
[4/4] Antigravity: ready (verified)Setup is idempotent — running it again refreshes recorded facts instead of duplicating state.
Use uze setup <name> to target one harness (claude, codex, opencode, agy — or their
stable ids claude-code, antigravity).
The installer output is buffered per harness under $UZE_HOME/state/logs/setup-<id>.log;
use --verbose to stream it.
Add a plugin
Project shorthand adds a plugin from a marketplace to the current project:
$ uze flow@ai
Claude Code: native (plugin:flow)
Codex: native (plugin:flow)
OpenCode: native (skills/flow)
Antigravity: native (plugin:flow)Machine-scoped verbs (add, remove, update, market, plugin, harness) manage the
machine-wide Store; project-scoped verbs (context, plus install/remove against
agents.lock) manage the current project. Neither touches the other's state.
Check the health
$ uze doctor # store, harness detection, attachment health, ledger
$ uze status # how this project's context reaches each harnessTerminal UI
Run uze with no arguments for the terminal UI: overview, marketplace, plugins with per-harness
delivery, harness drawer with compatibility per capability, and doctor.
A fresh project
On a new clone, agents.lock records the project's plugin set:
$ uze install # install this project's environment from agents.lockWhat happens next
- Concepts — the model behind the loop.
- Creating a plugin — the canonical layout, and how to publish one.
- Harnesses — what each harness gets, natively.
- CLI reference — every command.