# Installing the CRE CLI on macOS and Linux
Source: https://docs.chain.link/cre/getting-started/cli-installation/macos-linux
Last Updated: 2026-05-08

> For the complete documentation index, see [llms.txt](/llms.txt).

This page explains how to install the CRE CLI on macOS or Linux. The recommended version at the time of writing is ****.

## Select your operating system

- [macOS / Linux](/cre/getting-started/cli-installation/macos-linux)

- [Windows](/cre/getting-started/cli-installation/windows)

## Installation

Choose your installation method:

- **[Automatic installation](#automatic-installation)** - Quick setup with a single command
- **[Manual installation](#manual-installation)** - Download and install the binary yourself

### Automatic installation

The easiest way to install the CRE CLI is using the installation script:

```bash
curl -sSL https://app.chain.link/cre/install.sh | bash
```

This script will:

- Detect your operating system and architecture automatically
- Download the correct binary for your system
- Verify the binary's integrity
- Install it to `$HOME/.cre`
- Make the binary executable

After the script completes, verify the installation:

```bash
cre version
```

**Expected output:** 

> **NOTE: macOS Gatekeeper**
>
> If you see warnings about "unrecognized developer/source" on macOS, run:

### Manual installation

If you prefer to install manually or the automatic installation doesn't work for your environment, follow these steps:

The CRE CLI is publicly available on GitHub. Visit the releases page and download the appropriate binary archive for your operating system and architecture.

> **NOTE: Which file should I download?**
>
> The file you need depends on your operating system and CPU architecture:
>
> - On **macOS** (darwin), run uname -m:
>   - `arm64` (Apple Silicon) → Download `cre_darwin_arm64.zip`
>   - `x86_64` (Intel) → Download `cre_darwin_amd64.zip`
> - On **Linux**, the binary depends on both your architecture and OS version. First, run uname -m to check your architecture, then lsb\_release -rs to check your Ubuntu version:
>   - **Ubuntu 22.04 or older**:
>     - `x86_64` (AMD/Intel) → Download `cre_linux_amd64_ldd2-35.tar.gz`
>     - `aarch64` (ARM) → Download `cre_linux_arm64_ldd2-35.tar.gz`
>   - **Ubuntu 24.04 or newer**:
>     - `x86_64` (AMD/Intel) → Download `cre_linux_amd64.tar.gz`
>     - `aarch64` (ARM) → Download `cre_linux_arm64.tar.gz`
>
> **Note:** The `ldd2-35` binaries are compiled for older glibc versions (2.35 and below). If you're using a non-Ubuntu Linux distribution, check your glibc version with ldd --version and use the `ldd2-35` binary if your version is 2.35 or lower.

After downloading the correct file from the releases page, move on to the next step to verify its integrity.

#### 1. Verify file integrity

Before installing, verify the file integrity using a checksum to ensure the binary hasn't been tampered with:

**Check the SHA-256 checksum**

Run the following command in the directory where you downloaded the archive (replace the filename with your specific binary):

```bash
shasum -a 256 cre_darwin_arm64.zip
```

**Verify against official checksums**

Compare the output with the official checksum from the [CRE CLI releases page](https://github.com/smartcontractkit/cre-cli/releases):

1. Go to [https://github.com/smartcontractkit/cre-cli/releases](https://github.com/smartcontractkit/cre-cli/releases)
2. Find the release version you downloaded (e.g., )
3. Under the **Assets** section, locate your downloaded file
4. Compare the SHA-256 checksum shown next to the file with your command output

**Example:** For `cre_darwin_arm64.zip` in release , you'll see something like:

```
cre_darwin_arm64.zip
sha256:1359415a1f1baee7643107b82b3a0589a3627aef71018644e5c488960a97e955
```

If the checksums match, the file is authentic and safe to install. If they don't match, do not proceed with installation and contact the Chainlink team for assistance.

#### 2. Extract and install

1. **Navigate** to the directory where you downloaded the archive.

2. **Extract the archive**

   For `.tar.gz` files:

   ```bash
   tar -xzf cre_linux_arm64.tar.gz
   ```

   For `.zip` files:

   ```bash
   unzip cre_darwin_arm64.zip
   ```

3. **Rename the extracted binary to `cre`**

   ```bash
   mv cre_{CRE_CLI_VERSION}_darwin_arm64 cre
   ```

4. **Make it executable**:
   ```bash
   chmod +x cre
   ```
   **Note (macOS Gatekeeper)**: If you see warnings about "unrecognized developer/source", remove extended attributes:
   ```bash
   xattr -c cre
   ```

#### 3. Add the CLI to your PATH

Now that you have the `cre` binary, you need to make it accessible from anywhere on your system. This means you can run `cre` commands from any directory, not just where the binary is located.

**Recommended approach: Move to a standard location**

The easiest and most reliable method is to move the `cre` binary to a directory that's already in your system's PATH. For example:

```bash
sudo mv cre /usr/local/bin/
```

This command moves the `cre` binary to `/usr/local/bin/`, which is typically included in your PATH by default.

**Alternative: Add current directory to PATH**

If you prefer to keep the binary in its current location, you can add that directory to your PATH:

1. **Find your current directory:**

   ```bash
   pwd
   ```

   Note the full path (e.g., `/Users/yourname/Downloads/cre`)

2. **Add to your shell profile** (choose based on your shell):

   For **zsh** (default on newer macOS):

   ```bash
   echo 'export PATH="/Users/yourname/Downloads/cre:$PATH"' >> ~/.zshrc
   source ~/.zshrc
   ```

   For **bash**:

   ```bash
   echo 'export PATH="/Users/yourname/Downloads/cre:$PATH"' >> ~/.bash_profile
   source ~/.bash_profile
   ```

   Replace `/Users/yourname/Downloads/cre` with your actual directory path from step 1.

3. **For temporary access** (this session only):
   ```bash
   export PATH="$(pwd):$PATH"
   ```

#### 4. Verify the installation

**Test that `cre` is accessible:**

Open a **new terminal window** and run:

```bash
cre version
```

**Expected output:**



**If it doesn't work:**

- Make sure you opened a **new terminal window** after making PATH changes
- Check the binary location: `which cre` should return the path to your installation
- Check that the binary has execute permissions: `ls -la $(which cre)`
- Verify your PATH includes the correct directory: `echo $PATH`

#### 5. Confirm your PATH (troubleshooting)

If you're having issues, check what directories are in your PATH:

```bash
echo "$PATH" | tr ':' '\n'
```

You should see either:

- `/usr/local/bin` (if you moved the binary there)
- Your custom directory (if you added it to PATH)

## Next steps

Now that you have the `cre` CLI installed, you'll need to create a CRE account and authenticate before you can use it.

- **[Creating Your Account](/cre/account/creating-account)**: Create your CRE account and set up two-factor authentication
- **[Logging in with the CLI](/cre/account/cli-login)**: Authenticate the CLI with your account

Once you're authenticated, you're ready to build your first workflow:

- **[Getting Started — Part 1: Project Setup & Simulation](/cre/getting-started/part-1-project-setup)**: Initialize a new, blank CRE project and run your first "Hello World!" simulation.