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

# Clawdi CLI

> Connect Agents, work with shared Clawdi objects, and diagnose local integration.

The `clawdi` CLI is the main interface for adding an Agent that runs on your
computer. It registers Connected Agents, installs supported MCP integration,
syncs supported data, works with shared Clawdi objects, and controls the
background daemon.

The CLI also includes `clawdi deploy` for creating a Cloud Agent. That command
starts a remote deployment workflow; it does not turn local Agent software into
a Cloud Agent.

## Discover commands

Every command provides built-in help:

```bash theme={null}
clawdi --help
clawdi setup --help
clawdi memory --help
clawdi memory add --help
clawdi deploy --help
```

Use the deepest relevant `--help` command before scripting flags. The CLI help
shipped with your installed version is the most precise reference for that
version.

## Check local state

These commands do not print stored secret values:

```bash theme={null}
clawdi auth status
clawdi status
clawdi doctor
clawdi daemon status
```

* `auth status` identifies the current credential source.
* `status` summarizes authentication and sync activity.
* `doctor` checks authentication, API reachability, Agent paths, Vault
  metadata, and MCP configuration.
* `daemon status` reports the background sync service state.

## Preview sync and secret actions

Use dry-run modes when a command supports them:

```bash theme={null}
clawdi push --dry-run
clawdi pull --dry-run
clawdi run --dry-run --env-file .env.clawdi -- npm run dev
```

For secret workflows, `--dry-run` checks reference provenance without
requesting plaintext values.

## Use machine-readable output

Commands that advertise `--json` return machine-readable output. Confirm
support on the exact command before using it in automation:

```bash theme={null}
clawdi status --help
clawdi status --json
```

<CardGroup cols={2}>
  <Card title="Command map" icon="list" href="/cli/commands">
    Find the command family for a common task.
  </Card>

  <Card title="Core concepts" icon="blocks" href="/concepts/core-concepts">
    Use the canonical object names when reading commands and output.
  </Card>

  <Card title="Troubleshooting" icon="triangle-alert" href="/troubleshooting">
    Diagnose sign-in, setup, MCP, and daemon problems.
  </Card>
</CardGroup>