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

Agents come and go.
Your work stays.

One plugin and one AGENTS.md, native in every agent you run — today's and the ones after them. Run several at once; closing the terminal mid-run costs you nothing.

$ curl -fsSL https://uze.sh/i | sh
Get started

Linux and macOS, x86_64 or aarch64, checksum verified. Build from source on anything else.

The uze terminal: one project running a Claude Code agent and an OpenCode agent at once, each on its own branch in its own checkout, with the commit timeline of one beside them.
Run uze with no arguments. Ctrl+O switches between the workspace and the machine view.

Delivers natively to

  • One package, four native surfaces

    The Store owns a plugin’s bytes and writes nothing a harness reads. Each integration delivers them through the most native mechanism that harness has — a real plugin where one exists, a safe adapter only as a last resort.

    How delivery is decided
  • Semantics survive the trip

    A skill’s invocation policy, a hook’s effect, an agent’s frontmatter — each is translated into the vendor’s own encoding, or reported as adapted. uze never claims a route is native without a passing real-harness scenario.

    What travels, and how
  • One project context

    AGENTS.md is the portable baseline. Every harness reads it natively or through the one bridge uze maintains, inside regions it owns — never four instruction files drifting apart.

    How context reaches each harness
  • Agents that don’t collide

    Run several at once in one terminal. Each can take an isolated checkout on a branch of its own, readiness is read from Git rather than announced, and finished work comes home through a delivery you trigger — with the diff, the file tree and the project’s own diagrams a keystroke away.

    Inside the workspace

What each harness receives

A check means the capability is delivered. The word beside it is how: native through the harness's own mechanism, bridge or adapted where uze preserves the semantics another way and reports that it did. Every route is derived from the integration that implements it.

HarnessAGENTS.mdSkillsMCPAgentsHooksSessionPlugin
Claude Codebridgenativenativenativenativenativenative
Codexnativenativenativenativenativenativenative
OpenCodenativenativenativenativeadaptednative—
Antigravitynativenativenativenativenativenativenative

A dash means that route does not exist for the harness, and the capability arrives another way. Cursor CLI, Muse, PI are on the roadmap — cells appear when the integration lands. The full matrix, per capability.

Set it up once, on this machine.

uze detects the coding agents you already have, provisions the ones you don't through each vendor's own installer, and reports what it could not do rather than guessing.

Built with 🖤 by Romullo (@hiukky)

All product names, logos and brands are the property of their respective owners. uze names the coding agents it interoperates with for identification only, and is not affiliated with, endorsed by, or sponsored by any of them.