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

# Troubleshoot Clawdi

> Diagnose common Clawdi sign-in, Connected Agent, MCP, and daemon issues.

Start with the built-in diagnostic. It checks the current installation without
resolving stored Vault secrets.

```bash theme={null}
clawdi doctor
```

For a fuller snapshot, run:

```bash theme={null}
clawdi --version
clawdi auth status
clawdi status
clawdi daemon status
```

## Sign-in does not complete

Retry the browser flow:

```bash theme={null}
clawdi auth login
```

On SSH or a headless computer, print the sign-in URL instead:

```bash theme={null}
clawdi auth login --no-open
```

Open the URL on your local computer. If the browser cannot reach the loopback
callback on the remote computer, copy the complete failed callback URL from the
browser address bar and paste it into the CLI's masked prompt.

<Note>
  `clawdi auth login --manual` is for legacy Clawdi API keys and
  [self-hosting](/self-hosting). It does not authorize Cloud Agent deployment.
</Note>

## No supported Agent software is detected

First confirm the software is installed and its executable is on `PATH`. Then
identify it explicitly:

```bash theme={null}
clawdi setup --agent codex
```

Valid values are `claude_code`, `codex`, `hermes`, and `openclaw`. The
value identifies Agent software, not where the Agent runs.

## MCP tools are missing or stale

Refresh the selected Agent's setup, restart the daemon, and run the diagnostic
again:

```bash theme={null}
clawdi setup --agent codex
clawdi daemon restart
clawdi doctor
```

Replace `codex` with the matching Agent software value. Review any manual MCP
guidance that setup prints.

## Background sync is not running

Inspect the service before reinstalling anything:

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

If setup was originally run with `--no-daemon`, install the daemon explicitly:

```bash theme={null}
clawdi daemon install
```

## Memory search returns no results

Add a Memory, then search for a term it contains:

```bash theme={null}
clawdi memory add "Use npm for this Project"
clawdi memory search "npm"
```

## Check for a CLI update

```bash theme={null}
clawdi update --check
```

If an update is available:

```bash theme={null}
clawdi update
```

Native installations update through native release assets. npm installations
update through npm.

## Get more help

Before reporting a problem, collect the output of `clawdi --version`,
`clawdi doctor`, and the relevant command with `--help`. Follow the complete
[diagnostic redaction checklist](/support#redact-before-sending) before sharing
output.

<CardGroup cols={2}>
  <Card title="Support options" icon="life-buoy" href="/support">
    Choose email or a public issue and collect a safe diagnostic report.
  </Card>

  <Card title="Data and security" icon="shield-check" href="/trust/data-and-security">
    Review credential, Vault, third-party, and diagnostic boundaries.
  </Card>
</CardGroup>