Roadmap

StatusCopy Anchor Link

Beta. APIs, schemas, and harness integration behavior may change while the cross-harness model is validated. Linux and macOS releases are published on GitHub and installed by curl -fsSL https://uze.sh/i | sh; every version until v1 is an explicit pre-release. Native Windows is published too, installed by irm https://uze.sh/i | iex (see Installation).

Working todayCopy Anchor Link

• Harness management: detection, provisioning through official routes, and a cached readiness report for Claude Code, Codex, OpenCode and Antigravity.
• Capability portability: skills with invocation policy, MCP servers, portable agents, rules, and portable hooks (one script for every platform, with allow, ask, deny and transform), each delivered through the most native route the harness can preserve.
• Plugin requirements: a plugin names the programs its scripts need; uze add, uze install, uze status -m, uze inspect and uze doctor say what is missing, who needs it, and the command that installs it.
• Operator consent: everything a plugin can run (MCP servers, hooks, a skill's inline commands, requirement checks) is listed and approved before install, including what a cloned project's agents.yaml declares, and the commands a project's workspace runs wait for uze workspace allow.
• Native package delivery: a preserved vendor envelope where one exists, a deterministically generated one where it doesn't.
• Project context: AGENTS.md as the baseline, the operator's alone: uze writes nothing into it, and plugins speak through always_on rules.
• Reproducible project environments: agents.yaml declares, agents.lock pins each marketplace to a commit and each package to a digest, and git clone && uze install rebuilds both.
• Environment maintenance: doctor repairs the uze-owned artifacts it can prove are safe to rebuild, and escalates only real decisions.
• The terminal workspace: persistent panes, parallel agents in isolated checkouts, readiness read from Git, explicit delivery, and a conversation that survives a reboot.
• Extensions: Spec, for what a checkout intends and how far its tasks have got; Architect, for the project's own Mermaid diagrams drawn in the terminal; and Code, for a checkout's changes, files, history and map. A plugin can bring its own extensions, each running only with the grants you consented to; workspace@uze ships the official ones.
• Security: nothing a plugin, a project or an extension brings runs before you approve it, agents cannot answer for you, and uze's Git runs nothing a repository names. Security
• Freshness: uze status -m reports each package against its marketplace's mirror, and uze update moves the pins when you decide to.
• Records that survive an upgrade: a record written in a shape a build knows is carried across silently; only a shape with no rung is set aside.
• Theming and keys: one file restyles the CLI, the TUI and what a pane is told the terminal looks like; another rebinds every action, holding only what differs from the default.

In progressCopy Anchor Link

• Plugin versioning: a plugin is pinned to a commit today. A version a project can ask for by range is not decided yet.
• Agent containment beyond Linux: the seal between agent panes and the workspace's controls needs Linux with Landlock today.
• Runtime context projection: the PATH shim that reaches a harness without writing into the project is still experimental.
• Signed Windows binaries: Windows releases ship unsigned, which Smart App Control can refuse to run.
• Migration tooling and ecosystem expansion.

Planned harnessesCopy Anchor Link

Cells flip when the integration lands: the matrix on the compatibility page is generated from the integration code itself, so it can never silently rot.

Planned spec toolsCopy Anchor Link

Spec reads OpenSpec, Spec Kit, Superpowers and GSD today. Each of these is a table entry away, and the extensions page marks it supported when it lands.

The marketplaceCopy Anchor Link

The plugin ecosystem grows through the official marketplace (marketplace.json at the repository root, embedded in the binary as uze) plus any community marketplace registered with uze market add. The one official plugin today is plugins/uze, carrying the uze:init, uze:rules, uze:worktree, uze:architect and uze:author Skills.