Skip to main content
unbound setup <tool> is the normal path. Use the direct installer when the Unbound CLI isn’t on the machine, or when your organization runs Unbound on its own hosts. macOS and Linux
Windows — PowerShell has no process substitution, so download the installer first and run it:
If python isn’t on your PATH, use py -3 in its place. Replace gateway.getunbound.ai with your organization’s Unbound dashboard host, and the route with the one for your tool from the table below.

​
Routes

Run these without sudo — they configure the account you run them as. For fleet-wide deployment see Deploy AI Tools via MDM.

​
Flags

--domain only controls where the browser goes to authenticate. It does not move your model traffic.If your organization runs its own Unbound backend or gateway, pass --backend-url and --gateway-url as well. Passing --domain alone leaves the tool pointed at Unbound’s default hosts, and everything appears to install correctly.
Pass values in the --flag value form, with a space. The hooks installers — Claude Code hooks, Codex hooks, Cursor, Copilot, Augment — scan the argument list for exact flag names, so --domain=value, --api-key=value and the rest are read as unknown arguments and silently ignored. On its own that stops the run with Missing required argument: --domain or --api-key even though you passed it, and alongside --api-key it installs successfully but records no dashboard host. --config-dir is the one exception there and accepts either form. The gateway installers parse arguments properly and take either form — but use the space form everywhere and you never have to remember which is which.These installers have no --help — the table above is the flag list.

​
On a managed device

On an MDM-managed device the Claude Code, Codex, Cursor and Augment installers stop and change nothing, naming the tool — Skipped — Claude Code is managed by your organization (MDM), and likewise for the other three. They exit with status 3. The Copilot installer has no such guard and will install over an MDM deployment. That’s expected: your MDM deployment is already in place and a per-user install can’t override it.

​
If the browser step doesn’t finish

The installer waits for a callback from the dashboard you named in --domain. If it hangs, or ends with No api_key found in callback. Exiting., the host you passed isn’t the dashboard that can mint a key for your organization — check it against the URL you use to sign in.