FAQ
Short answers to the questions people ask first
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. It writes nothing into a file you author, AGENTS.md included. In your
project it writes only agents.yaml, agents.lock and the rule files of the
plugins you declare, each plugin's in a folder of its own under
.agents/rules/, with one entry per folder in .agents/rules.json. Every other
entry of that manifest is left as you wrote it. A copy you edit is reported,
never overwritten. See Project context.
Does uze send anything over the network?
It fetches the marketplaces you registered, to install and update plugins. uze
checks GitHub for a new release of itself at most once an hour, from the
workspace and in the background after a command. A uze placed by the install
script installs a release a day after it is first seen; UZE_AUTOUPDATE=off
stops that, and notify only tells you. In the workspace, uze talks to your
project's own Git remote: it fetches the target branch, looks for open pull
requests on an agent's branch, and pushes when delivery is push.
uze setup runs each agent's official installer. uze never talks to a model
provider, and 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, and ~/.uze/shims too: all three are rebuilt the next time they are
needed. ~/.uze/sources holds the plugins you installed, which come back only
by installing them again. ~/.uze/store is what your agents read, and deleting
it uninstalls their plugins. ~/.uze/state is the one to keep: it records what uze
placed where, the marketplaces you registered, the commands you approved and
your agents' history. config.toml, keys.json and
themes/ are files you wrote.
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.