---
title: "Install the CLI"
description: "Install the anlyon CLI from npm (Node 20.3 or later), or use a standalone executable for Linux, macOS or Windows."
icon: "download"
---

Install the CLI from npm.

## npm

The npm package needs Node 20.3 or later. It has no runtime dependencies. The Anlyon SDK is bundled in.

```bash npm
npm install -g @anlyonhq/cli
```

```bash pnpm
pnpm add -g @anlyonhq/cli
```

Check the install:

```bash
anlyon --version
```

The version output also names the `@anlyonhq/sdk` version bundled into this build.

To run a single command without a global install:

```bash
npx @anlyonhq/cli --version
```

To upgrade, run the install command again. To remove it, `npm uninstall -g @anlyonhq/cli`.

## Supported platforms

| Platform | Architectures |
| --- | --- |
| Linux | x64, arm64 |
| macOS | x64 (Intel), arm64 (Apple silicon) |
| Windows | x64 |

The npm package runs wherever Node 20.3 or later runs.

## Standalone executables

A standalone executable embeds its own runtime, so it runs on a clean machine with no Node installed. Each GitHub release tagged `@anlyonhq/cli@<version>` carries one file per platform, with a `SHA256SUMS` file alongside:

| Platform | File |
| --- | --- |
| Linux x64 / arm64 | `anlyon-linux-x64`, `anlyon-linux-arm64` |
| macOS Intel / Apple silicon | `anlyon-darwin-x64`, `anlyon-darwin-arm64` |
| Windows x64 | `anlyon-windows-x64.exe` |

The release assets sit in the Anlyon source repository, which is private. Downloading one needs access to that repository. Without it, install from npm.

### Verify the download

Compare the file's SHA-256 hash with its line in `SHA256SUMS`:

```bash Linux
sha256sum anlyon-linux-x64
```

```bash macOS
shasum -a 256 anlyon-darwin-arm64
```

```powershell Windows
Get-FileHash anlyon-windows-x64.exe -Algorithm SHA256
```

### macOS and Linux

Make the file executable and move it onto your `PATH` as `anlyon`:

```bash
chmod +x anlyon-darwin-arm64
sudo mv anlyon-darwin-arm64 /usr/local/bin/anlyon
anlyon --version
```

Use the file name for your platform and architecture.

macOS may quarantine an unsigned download. Code signing and notarisation are not in place yet. If macOS refuses to run the file, clear the quarantine attribute before moving it:

```bash
xattr -d com.apple.quarantine anlyon-darwin-arm64
```

### Windows

Put `anlyon-windows-x64.exe` on your `PATH` as `anlyon.exe`. For example, in PowerShell, for the current user:

```powershell
$dir = "$env:LOCALAPPDATA\Programs\anlyon"
New-Item -ItemType Directory -Force $dir | Out-Null
Move-Item anlyon-windows-x64.exe "$dir\anlyon.exe"
[Environment]::SetEnvironmentVariable("Path", [Environment]::GetEnvironmentVariable("Path", "User") + ";$dir", "User")
```

Open a new terminal so it picks up the new `PATH`, then check:

```powershell
anlyon --version
```

## Next

[Log in](/cli/authentication) with `anlyon auth login`, or set `ANLYON_API_KEY` for automation.
