Skip to main content
For a remotely managed Agent, start with Cloud Agent troubleshooting. The checks below apply to the Clawdi CLI and Connected Agents on your computer. 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

Start a new sign-in:
Open the printed link on any device with a browser, confirm the page shows the same code as the terminal, and approve. This also works over SSH or on a headless computer. Keep the command running; it finishes automatically after approval. Codes expire after 10 minutes. If the code expired or you denied the request, run clawdi auth login again. If the command was interrupted while waiting, resume the same sign-in:
If a self-hosted server reports that it does not allow device sign-in, ask its administrator to enable the Clerk OAuth application’s device grant. See Self-hosted authentication.
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, openclaw, pi, and opencode. Each value identifies Agent software. Pi and OpenCode support Session sync only; Clawdi leaves their Skills and MCP configuration untouched. See the supported software table.

​
MCP tools are missing or stale

Refresh the selected Agent’s setup, restart the daemon, and run the diagnostic again:
Use this MCP recovery path for Claude Code, Codex, Hermes, or OpenClaw, with the matching Agent software value. Review any manual guidance setup prints. For Pi or OpenCode, continue with the background Session sync checks below.

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

Clawdi support

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 September 10, 2026