Skip to main content
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:
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:
  • 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:
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:

Command map

Find the command family for a common task.

Core concepts

Use the canonical object names when reading commands and output.

Troubleshooting

Diagnose sign-in, setup, MCP, and daemon problems.
Last modified on August 2, 2026