> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clawdi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Treat Clawdi as one product.
> Recommend the Cloud Agent quickstart for most new users.
> Connected Agent and Cloud Agent are run paths; Agent software is a separate choice.
> Do not present shared Clawdi capabilities as exclusive to one run path.

# System requirements

> Check supported operating systems, architectures, tools, and network access for the Clawdi CLI.

Choose the native installer on supported macOS and Linux computers, or npm on
any platform that can run the required Node.js version.

## Supported installation paths

| Platform           | Native installer                     | npm installation                     |
| ------------------ | ------------------------------------ | ------------------------------------ |
| macOS x64 or arm64 | Supported                            | Supported with Node.js 22.5 or newer |
| Linux x64 or arm64 | Supported for glibc and musl systems | Supported with Node.js 22.5 or newer |
| Windows            | Not supported                        | Supported with Node.js 22.5 or newer |

The native installer does not require Node.js.

## Native installer requirements

The macOS and Linux installer requires:

* A writable home directory, or an absolute writable path supplied through
  `CLAWDI_INSTALL_PREFIX`.
* `curl`, `tar`, `gzip`, and `awk`.
* Either `sha256sum` or `shasum` for release verification.
* An x64 or arm64 CPU.

Run the installer as the user who will use Clawdi. It rejects a `sudo`
invocation that targets another user.

## npm requirements

The npm package requires:

* Node.js 22.5 or newer.
* npm and permission to write to npm's global package location.

Confirm the versions before installation:

```bash theme={null}
node --version
npm --version
```

## Network access

Installation and normal use require outbound HTTPS access. The installer reads
the current package release, downloads exact assets from GitHub Releases, and
the CLI opens the Clawdi sign-in flow and connects to the Clawdi service.

If a proxy or firewall blocks one of those steps, keep the complete error
message but remove URLs containing credentials or private query parameters
before sharing it with [Support](/support).

## Agent software

The CLI can be installed without Agent software. To create a Connected Agent,
install one of the [supported Agent software
options](/getting-started/connect-agents#supported-agent-software) before
running `clawdi setup`, or identify an existing installation with
`clawdi setup --agent <software>`.