Browse / Software development / uze

uze

uze-sh

🧩 The terminal workspace for coding agents

Open uze-sh/uze → Checked against the four rules.

agent-skillsagentsagents-mdaiai-agentsantigravityclaudeclaude-codeclicodexcoding-agentsdeveloper-tools

Works with any agent

ships AGENTS.md, the cross-tool instruction file.

In its own words

README.mduze-sh/uze

Agents come and go. Your work stays.

Give every coding agent you use the same plugins and the same project instructions, and run several of them at once without one stepping on another. uze is not an agent itself: no model, no API key, your agents keep their own logins.

Install

Then follow the quickstart, or read the full documentation.

To take uze off the machine, run uze uninstall: it removes the program and leaves every plugin it delivered working. uze uninstall --purge also takes back everything it delivered to your coding agents and removes ~/.uze. Removing ~/.uze by hand is not supported: your coding agents read their plugins from it. If something in it was deleted or damaged, uze doctor reports it.

Two tools, one binary

Each works without the other: use the package manager with agents you start yourself, the workspace to run them, or both.

  • Package manager. Install a plugin once and Claude Code, Codex, OpenCode

and Antigravity each receive it through their own native mechanism. One AGENTS.md holds the project's instructions for all of them, and agents.yaml records the project's plugins, so a teammate gets the same setup with uze install.

  • Workspace. Run agents side by side in one terminal, each on its own

branch in a checkout of its own. See what each one changed, bring the work home when it is ready, and close the terminal without losing any of it.

Quoting 54% of the README. Read the rest on GitHub ↗

Read from the repository's git tree on 2026-08-17.