1. Requirements and installation

Use Node.js 22.19 or newer. npm is the beta distribution channel; signed standalone archives are unavailable. The resolved beta version for this page is 0.81.0-beta.20.

npm install --global --ignore-scripts @adrouter/cli@beta
adrouter --version
adrouter --json doctor

Compare the installed version with the release notes and use the published checksums and repository provenance when inspecting artifacts.

2. Start in the intended project

Run adrouter from the project you intend to use. Review the workspace trust prompt and any project-local .adrouter resources before accepting. A trusted project may influence instructions and tool behavior.

3. Sign in and approve the installation

  1. Inside the TUI, run /login adrouter.
  2. Sign in at the opened AdRouter WebUI, return to the CLI, and choose the native Done action.
  3. Approve only the installation request you recognize. If automatic browser launch fails, use the displayed Open or Copy option; Quit cancels.

The CLI stores an installation key and rotating refresh credential in its permissions-protected local auth file; access tokens remain memory-only. Use /logout adrouter to attempt remote revocation and remove local installation secrets.

4. Use and approve tools

Select one of the tool-qualified models shown by adrouter --offline --list-models adrouter. Inspect each proposed command and mutation. Approvals do not make a command safe automatically. Run /ads to inspect or disable sponsored compute; sponsor metadata stays outside the model conversation and tools.

5. Update and uninstall

npm install --global --ignore-scripts @adrouter/cli@beta
adrouter --version
adrouter --json doctor
npm uninstall --global @adrouter/cli

Uninstalling the npm package does not delete ~/.adrouter. That directory can include credentials, profiles, sessions, and trust decisions; remove it only when you intend to delete that local state. Backups of it are sensitive credential material.

CLI repositoryCompatibility update