FAQ

Is uze a coding agent?

No. uze has no model and never calls one. It installs plugins into Claude Code, Codex, OpenCode and Antigravity, and runs those agents in the workspace; you start and talk to each one exactly as you do today.

Do I need an API key?

No. Each agent keeps its own login and subscription. uze never talks to a model provider.

Why not a symlink or a script?

A symlink works when every harness reads the same file in the same format. They don't. Each harness has its own plugin layout. Codex has no Markdown agent format, so an agent becomes a TOML file there. A skill only the user may run is written differently in each harness. Hooks run through a different mechanism in each one.

A script can do the translation once. What it can't do is take it back safely. For everything it places, uze keeps a receipt. That is how it updates or removes a plugin without touching what you or another tool put next to it.

Will uze overwrite my files?

No. In a file you own, uze writes only between its own <!-- uze:begin … --> and <!-- uze:end … --> markers. If a file already holds content uze doesn't own where it would write, uze reports it and leaves the file alone. See Project context.

Does uze send anything over the network?

It fetches the marketplaces you registered, to install and update plugins. The workspace checks GitHub for a new release when it opens and every hour after. Release builds contain no telemetry.

What if a harness can't do something a plugin needs?

You are told. Each capability is reported as native, adapted, or unsupported for each harness, with the reason. It never drops a capability silently. See Harness support.

Can I delete ~/.uze/runtime or ~/.uze/cache?

Yes. Both are rebuilt the next time they are needed. ~/.uze/store holds the plugins you installed, which come back only by installing them again. ~/.uze/state is the one to keep: it records what uze placed where.

Does it work on Windows?

Yes, natively. Windows 10 22H2 and Windows 11, x64 or Arm, install with irm https://uze.sh/i | iex. The binary is not signed yet, so Smart App Control can refuse it. WSL works with the Linux command too, and you can build from source on anything Rust targets. See Installation.

How do I take it off?

See Removing uze.