# Install the CLI

Install the foxora command with the package manager you already use — npm, Homebrew, Scoop, or a one-line install script. Every method drops the foxora binary on your PATH and provisions the runtime on first use.

## Install the foxora command

Pick the tab that matches how you like to install tools.

- 01Install the CLInpmHomebrewScoopShellPowerShell# any OS with Node 16+
npm install -g foxoraCopyNot on your PATH yet?The script installers fall back to ~/.local/bin when a system dir isn’t writable. If your shell can’t find foxora afterwards, add that directory to your PATH and restart the shell — the installer prints the exact line to add.
- 02Provision the runtimeThe first time you run anything, Foxora fetches the runtime (engine, memory, workspace, and a bundled bun) into ~/.foxora/runtime. You can trigger it explicitly:bashCopyfoxora setupfoxora setupfoxora setup — provisioning the engine · memory · workspace · bun
- 03Verify the installConfirm the binary is on your PATH and print its version:bashCopyfoxora --version
# → foxora 5.0.3Then run a full diagnostic — it checks the platform, the runtime, the engine, your account, and the gateway in one shot:bashCopyfoxora doctor

## Keep it current

foxora update updates the CLI and keeps the runtime matched. It is channel-aware: if you installed through a package manager it points you at the right upgrade command instead of fighting it.

```
foxora update
```

> Next: sign inWith the CLI installed, the next step is to authorize it against your account so it can reach the gateway on your behalf.