Skip to main content
The unbound setup command configures AI coding tools to route through Unbound. It handles authentication, environment variables, and tool-specific config files automatically. If you are not logged in and --api-key is not provided, the browser opens automatically to authenticate before setup begins.

​
Interactive setup

Run with no arguments to select tools from an interactive menu:

​
Default bundle

Install Cursor, Claude Code (hooks), Codex (hooks), Copilot (hooks), and Augment (hooks) in one command:

​
Individual tools

​
Cursor

​
Claude Code

Claude Code supports two modes:
Run without a flag for interactive mode selection.
The bare unbound setup claude-code (no flag) and unbound setup codex (no flag) commands open an interactive prompt to pick a mode. In a non-interactive shell (CI, SSH with < /dev/null, MDM bootstrap) the prompt has no input source and the command exits immediately without writing any config. Always pass --gateway or --subscription explicitly in headless environments.

​
Gemini CLI

​
Codex

​
GitHub Copilot

Hooks-based — works with both the VS Code extension and the copilot CLI on your existing Copilot subscription.

​
Augment Code

Hooks-based — works with both the Augment VS Code extension and the Auggie CLI.

​
Instruction-only tools

These tools require manual configuration. The CLI prints the API key and base URL to enter in each tool’s settings.

​
One-step login + setup

Combine authentication and setup in a single command with --api-key:
When specifying multiple tools in one command, use the explicit form names:

​
Remove configuration

Remove every tool’s configuration in one command:

​
Uninstall everything

unbound nuke (alias unbound uninstall) removes Unbound entirely and returns the CLI to a fresh state: it clears tool configuration and deletes your stored credentials (~/.unbound/config.json). When it finishes, run unbound login (or unbound onboard) to set things up again. The scope follows your privileges — no flag to pick:
Add --yes to skip the confirmation prompt.

​
Setup flags

​
One-step onboarding

unbound onboard runs setup --all followed by device discovery in a single command. Useful for new user enrollment:

​
MDM setup (admin, requires root)

Scope is automatic: run unbound setup / unbound onboard with sudo to configure every user on the device (MDM/org scope), or without sudo to set up just the current user. For organization admins enrolling devices via MDM, run unbound setup with sudo to configure all users on the device:
For device-wide onboarding in one step:
MDM setup requires root and is intended for administrators deploying Unbound across an organization’s device fleet. See MDM Integrations for deployment guides.