Skip to main content
Start with the built-in diagnostic. It checks the current installation without resolving stored Vault secrets.
For a fuller snapshot, run:

​
Sign-in does not complete

Retry the browser flow:
On SSH or a headless computer, print the sign-in URL instead:
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.
clawdi auth login --manual is for legacy Clawdi API keys and self-hosting. It does not authorize Cloud Agent deployment.

​
No supported Agent software is detected

First confirm the software is installed and its executable is on PATH. Then identify it explicitly:
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:
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:
If setup was originally run with --no-daemon, install the daemon explicitly:

​
Memory search returns no results

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

​
Check for a CLI update

If an update is available:
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 before sharing output.

Support options

Choose email or a public issue and collect a safe diagnostic report.

Data and security

Review credential, Vault, third-party, and diagnostic boundaries.
Last modified on August 2, 2026