Glossary
The words uze uses, one line each
Each entry is the short version. The link goes to the page that explains it.
Packages
Harness. A coding agent uze delivers to: Claude Code, Codex, OpenCode or Antigravity. See Harnesses.
Plugin (package). What you install once. A directory holding skills, MCP servers, agents, hooks and rules. See Creating a plugin.
Marketplace. A Git repository with a marketplace.json, remote or cloned
locally. Every plugin is resolved through one. uze ships inside the
binary, and a project declares its plugins with no source.
Sources. Where uze keeps a plugin's bytes, under ~/.uze/sources. The
single source of truth. No harness reads it directly.
Store. What the harnesses read, under ~/.uze/store: one directory per
vendor, holding one build of each plugin. Deleting it uninstalls their plugins.
Capability. One kind of thing a plugin declares: a skill, an MCP server, an agent or a hook. See Plugin format.
Invocation policy. Who may run a skill: the model, the user, or both. The
invoke: {model, user} block in SKILL.md.
Trust. Your approval for anything a plugin can execute: MCP commands, hook
handlers, Skills and agents that run commands or grant themselves tools, and the
programs uze asks for their version to check requirements. You are asked before
they are installed, and again when any file of the plugin changes. --trust
answers yes, for CI. See Security.
Delivery
Integration. The part of uze that knows one harness. Everything vendor-specific lives there.
Delivery route. How a capability reaches a harness. The first that works wins, in this order: native, generated native, safe adaptation, unsupported. See How delivery works.
Envelope. A harness's own plugin format. The one a plugin ships is used, or one is generated when it is missing.
Projection. Writing a harness's own view of something uze owns: a plugin directory, a config entry, a bridge. A projection can always be deleted and rebuilt.
Receipt. The record of an artifact uze placed. Only what a receipt says it owns is ever changed or removed. See How delivery works.
Drift. An owned artifact that no longer matches its receipt. It is reported, and nothing overwrites it.
Shim. A link in ~/.uze/shims that starts the real harness binary, used
only by the workspace: its panes put the shims first on PATH, and no shell
of yours is edited. It brings an agent back to its conversation after a
reboot, and carries a project's .agents/ into a harness that does not read
it. Experimental. See
Terminal.
Projects
Machine scope. What lives in ~/.uze: the store, your agents' setup,
marketplaces and configuration. -m makes a command act on it alone.
Project scope. What lives in a project: agents.yaml, agents.lock and,
under .agents/rules/, the rules of the plugins it declares. A command run
inside a project maintains them. AGENTS.md is yours, and uze writes nothing
into it.
agents.yaml. What the project declares: marketplaces and plugins and,
under workspace:, how its agents work, what they are asked at each state, and
where its artifacts live. You write it. See Project files.
agents.lock. What resolving agents.yaml produced: a commit per
marketplace and a digest per plugin. Written by uze; deleting it loses nothing.
Workspace
Workspace. The terminal UI that opens when you run uze workspace.
See Workspace.
Space. A named group of agents in the workspace. It has no directory of its own: each agent in it keeps its own project. See Space.
Terminal runtime. A local server that owns the terminals, so an agent keeps running after you close the UI.
Primary checkout. The project's own working tree, on the branch you have checked out. An agent works here until it is given a worktree.
Worktree. A Git worktree of its own for one agent, at .worktrees/<id>, on
branch agent/<id> until the agent names its work, which renames the
branch. An agent gets one at launch when workspace.worktree is
always, or when you move it with To worktree.
Slot. A worktree uze made and reuses for the next agent instead of creating a new one. Its making is recorded, and only a checkout uze made is ever reused or removed. See Running agents.
Subagent checkout. A slot an agent asked for with uze agent work split
for one of its subagents. Its work comes back to the agent with
uze agent work join. See Subagents.
Delivery (of work). Rebasing an agent's branch onto the target, running the
project's gate, then fast-forwarding the local target (merge) or pushing the
branch (push). No pull request is opened: what the agent is asked next is the
project's actions. See Bringing the work home.
Shelf. Where an agent's unfinished work is kept once its checkout goes back
to the pool: one commit per agent at refs/uze/shelf/<task>, in the
repository's own Git directory, resumed from any checkout. See
Work nobody finished.
Recent. The sidebar mode listing every agent no pane carries, across every project, and what waits on you. See Recent.
Command approval. Your yes to the exact setup and gate lines a
project's agents.yaml runs, once per project on each machine, asked again
when a line changes. Only a person at a terminal can give it. See
Approving the commands.
Extension. Something the workspace shows beside your agents. Three are built in (Spec, Architect and Code), and a plugin can declare more, which run nothing until you allow what they may reach and enable them. See Extensions and writing one.
Conformance Lab. Tests that run each real harness binary in a sealed Docker world, with no internet and no tokens. See Development.