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. With CLI 0.15.7 or newer, you can also list and manage Agents, control Cloud Agent lifecycle and plugins, manage uploaded Sessions and Cloud AI Providers, and inspect Wallet transactions and usage. Use clawdi deploy to create a Cloud Agent. See CLI commands for examples and Authentication for access limits. Scripting guidance below follows CLI 0.16.

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

​
Scripting and automation

​
Use machine-readable output

Commands that advertise --json return machine-readable output. Confirm support on the exact command before using it in automation. Starting in CLI 0.16, pass --json explicitly: piped output stays human-readable. JSON output is one object with a string schemaVersion, such as "clawdi.agentList.v1", and lists appear in a named array inside the object. CLI 0.16 moved doctor, session list/search, memory list/search, project list, deploy, wallet status/transactions/usage, and ai-provider list/export to v2 objects; update scripts that read them. Results go to stdout; errors, progress, and prompts go to stderr. Check the exit code and allow additional fields when parsing versioned output:

​
Confirm destructive actions

Pass --yes to confirm destructive commands in scripts. --json does not imply confirmation. Starting in CLI 0.15.18, commands that delete or revoke something require --yes without an interactive terminal.

​
Check exit codes

​
Control color and updates

Set a non-empty NO_COLOR environment variable or pass --no-color to disable color. Every command accepts --no-color before the -- separator. Opt out of CLI and daemon background auto-updates with CLAWDI_NO_AUTO_UPDATE=1, or save the preference:

CLI commands

Find the command family for a common task.

Core concepts

Understand the objects named in commands and output.

Troubleshooting

Diagnose sign-in, setup, MCP, and daemon problems.
Last modified on October 7, 2026