> ## 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.

# Connect a local Agent

> Install the Clawdi CLI and connect Agent software that runs on your computer.

This is the **Connected Agent** quickstart. Use it when Agent software already
runs on your computer and needs access to that computer or its local tools.

<Note>
  Most new users should start with the [Cloud Agent
  quickstart](/cloud-agents/deploy), which does not require a local
  installation.
</Note>

## Before you begin

* Review [System requirements](/installation/requirements). On macOS or Linux,
  the native installer does not require Node.js. On Windows, or for an
  npm-managed installation, install Node.js 22.5 or newer.
* Install at least one [supported Agent software
  option](/getting-started/connect-agents#supported-agent-software) if you want
  `clawdi setup` to detect it automatically.

## Steps

<Steps>
  <Step title="Install the Clawdi CLI">
    <Tabs>
      <Tab title="macOS and Linux">
        ```bash theme={null}
        curl -fsSL https://clawdi.ai/install.sh | sh
        ```

        The native installer selects a release for your operating system and
        CPU architecture. It installs to `~/.local` by default.
      </Tab>

      <Tab title="Windows or npm">
        ```bash theme={null}
        npm i -g clawdi
        ```

        This path requires Node.js 22.5 or newer.
      </Tab>
    </Tabs>

    Confirm the command is available:

    ```bash theme={null}
    clawdi --version
    ```
  </Step>

  <Step title="Sign in">
    ```bash theme={null}
    clawdi auth login
    ```

    Clawdi opens a browser for sign-in. On SSH or a headless machine, use
    `clawdi auth login --no-open` instead. See
    [Authentication](/account/authentication) for the callback and local
    credential safeguards.
  </Step>

  <Step title="Connect the Agent">
    ```bash theme={null}
    clawdi setup
    ```

    Select the detected Agent software you want to connect. Setup registers an
    Agent, adds the supported Clawdi MCP entry, installs the bundled Clawdi
    Skill, and starts background sync by default.
  </Step>

  <Step title="Check the setup">
    ```bash theme={null}
    clawdi doctor
    ```

    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.
  </Step>
</Steps>

<Check>
  Your Connected Agent is ready. Start a new Agent Session and ask what Clawdi
  tools are available, or add a Memory from the CLI with
  `clawdi memory add "I prefer concise status updates"`.
</Check>

## Next steps

<CardGroup cols={2}>
  <Card title="Connect another local Agent" icon="plug" href="/getting-started/connect-agents">
    Select a specific Agent software option and verify its local integration.
  </Card>

  <Card title="Learn the core concepts" icon="blocks" href="/concepts/core-concepts">
    Understand the canonical objects that stay consistent across Agent
    workflows.
  </Card>

  <Card title="Use shared capabilities" icon="book-open" href="/guides">
    Follow task guides for Projects, Memories, Sessions, Skills, Vaults,
    Connectors, Channels, and AI Providers.
  </Card>

  <Card title="Keep the CLI current" icon="refresh-cw" href="/installation/update">
    Check for a release and update through the same installation owner.
  </Card>
</CardGroup>