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

# Install the CLI

> Install Autter, choose a storage mode, and verify AI authorship tracking.

Install Autter once on each developer machine. You do not need per-repository setup.

## Requirements

* Git
* A supported macOS, Linux, WSL, or Windows environment
* At least one supported coding agent for automatic attribution

## Install

<Tabs>
  <Tab title="macOS, Linux, or WSL">
    Run the installer:

    ```bash theme={null}
    curl -sSL https://autter.dev/install.sh | bash
    ```
  </Tab>

  <Tab title="Windows">
    Run PowerShell without administrator privileges:

    ```powershell theme={null}
    powershell -NoProfile -ExecutionPolicy Bypass -Command "irm https://autter.dev/install.ps1 | iex"
    ```
  </Tab>
</Tabs>

<Warning>
  Do not run Autter as root or with `sudo`. Elevated installation can create files your normal user cannot update.
</Warning>

The installer places Autter in `~/.autter/bin`, adds it to your user `PATH`, configures supported coding agents and editors, and starts the background service.

Close and reopen your terminal and IDE after installation. Interactive macOS, Linux, and WSL installs start onboarding automatically. If the installer runs without an interactive terminal, complete onboarding later with `autter onboard`.

## Complete onboarding

The installer asks whether you want local-only or connected mode.

<Frame caption="Replace this placeholder with the final onboarding terminal screenshot.">
  <img src="https://mintcdn.com/autter/ZqVSJE8MeDV-Tn7Q/images/placeholders/cli-onboarding.svg?fit=max&auto=format&n=ZqVSJE8MeDV-Tn7Q&q=85&s=000d9ce140bbde87d2a06f06348fb178" alt="Placeholder for the Autter CLI onboarding choices" width="1440" height="900" data-path="images/placeholders/cli-onboarding.svg" />
</Frame>

<Tabs>
  <Tab title="Local-only">
    Choose local-only mode to keep prompts on the machine and use Git notes for attribution.

    You can select it again later:

    ```bash theme={null}
    autter onboard --local --force
    ```
  </Tab>

  <Tab title="Connected">
    Choose connected mode to sign in and sync attribution to the Autter platform.

    You can start the flow later:

    ```bash theme={null}
    autter onboard
    ```

    To select connected mode directly, run `autter onboard --connect`.

    If onboarding cannot complete, use the [PAT fallback](/cli/connect-platform#pat-fallback).
  </Tab>
</Tabs>

## Verify the installation

```bash theme={null}
autter --version
autter debug
autter whoami
```

* `autter --version` prints the installed version.
* `autter debug` checks the installation and integrations.
* `autter whoami` shows whether the CLI is connected.

## Verify an agent integration

Start a fresh coding-agent session after installation. Ask the agent to edit a tracked file, then run:

```bash theme={null}
autter status
```

Commit the change and inspect its attribution:

```bash theme={null}
git commit -am "Test Autter attribution"
autter stats HEAD
```

<Tip>
  If you installed a new coding agent after Autter, run `autter install-hooks` to refresh integrations.
</Tip>

## Update Autter

```bash theme={null}
autter upgrade
```

Use `autter upgrade --force` to reinstall the latest release.

## Next step

<Card title="Connect to the platform" icon="cloud" href="/cli/connect-platform">
  Learn what connection enables and how repository data is routed to your organization.
</Card>