Skip to main content
The Clawdi CLI connects Agent software on your computer and works with shared Clawdi objects. Installing the CLI does not create a Cloud Agent or install Agent software.
Review the system requirements before you install. The native installer is the shortest path on macOS, Linux, and Windows, with no Node.js required.

​
Native installation

1

Install the Clawdi CLI

Run the installer as your normal user:
Run without sudo.
For a package-manager alternative, follow the npm installation instructions, then continue with sign-in below.
2

Sign in

Open the printed sign-in link, confirm the page shows the same code as the terminal, and approve. The CLI finishes automatically. On SSH or a headless machine, open the link on any device with a browser. See Authentication for code expiry, interrupted sign-ins, and local credential safeguards.
3

Connect the Agent

Select the detected Agent software you want to connect. Setup registers an Agent and starts background sync by default. It also adds the Clawdi MCP entry and bundled Skill where supported. Pi and OpenCode sync Sessions only; see the support table.
4

Check the setup

A healthy setup reports successful checks for authentication, API reachability, registered Agents, Vault metadata, and Clawdi MCP. Agent software not installed on this computer can appear as unavailable without preventing an installed Agent from working.

​
macOS and Linux

The installer selects the release for your operating system and CPU, verifies the release artifact against its SHA-256 manifest entry, and installs under ~/.local by default. If ~/.local/bin is not on PATH, the installer adds it to your shell profile. Open a new terminal, or in bash or zsh run export PATH="$HOME/.local/bin:$PATH" to update the current shell. To skip updating your shell profile:
To inspect the installer before running it:

​
Choose a different prefix

The prefix must be an absolute path that your user can write. The executable goes in <prefix>/bin and versioned files go in <prefix>/share/clawdi.

​
Windows

The PowerShell installer installs to %USERPROFILE%\.local\share\clawdi\current and adds that directory to your user PATH. It requires neither Node.js nor administrator access. Open a new terminal after installing. Use clawdi update to update in place. A native installation on CLI 0.15.8 or earlier cannot update itself; run the installer again once. To leave PATH unchanged, set the opt-out before running the installer:
The default release channel is latest. To select beta, set $env:CLAWDI_CHANNEL='beta' before running the installer.

​
npm installation

Install Node.js 24 or newer, then use npm:
Use this alternative on macOS, Linux, or Windows when you prefer npm to own the installation.

​
Verify the installation

If the shell cannot find clawdi, open a new terminal and check the install directory is on PATH.

​
Install an exact release

Use an exact version when reproducing an environment or testing an upgrade.
Replace X.Y.Z with a published semantic version. The native installer accepts the version without the release tag prefix. Find published versions on GitHub Releases or npm.

​
Continue setup

Follow Connect a local Agent for the complete Connected Agent flow, or read Authentication before you sign in.
Last modified on October 6, 2026