clawdi <command> --help for the
arguments, options, and examples shipped with your CLI version. Object names
follow the definitions in Core concepts.
The Session sharing/export, Memory update, remote Skill management, and native
provider deployment workflows require CLI 0.14.57 or newer. Check
clawdi --version and update the CLI when needed.
Self-hosted services also need the corresponding API support.
Use CLI 0.15.7 or newer for the new Agent, uploaded Session, Wallet, and
Cloud resource commands below. Examples follow CLI 0.16, where scripts pass
--json explicitly and confirm destructive commands with --yes; see
Scripting and automation.
Get started and stay healthy
Manage Agents
Use the Agent UUID from
clawdi agent list. For lifecycle commands,
--no-wait returns when the server accepts the operation. Plugin changes
return when accepted; check agent plugins list to confirm they were applied.
Sync and inspect Agent data
Use the uploaded Session UUID from
session list --uploaded for removal:
Work with shared context
Use Sessions for share scopes and link IDs, and
Skills for the distinction between local software names,
Cloud Agent IDs, and Library Skill IDs. Manage account notifications and
payment details through the dashboard.
link and unlink for Agent Project access. attach and detach remain
compatible aliases for existing scripts.
Work with secrets and AI Providers
After sign-in,
ai-provider list, edit, and remove work with Cloud
AI Providers. The local catalog remains available for import and export;
without sign-in, list shows only local entries. Use the provider ID from
ai-provider list for edits and removal.
vault request --wait waits up to five minutes for the secret to be supplied.
The Vault must already be attached to the selected Project.
Inspect your Wallet
Deploy a Cloud Agent
This workflow is available only for Cloud Agents. Run
clawdi deploy --help
for current choices and automation requirements. See Automate Cloud Agent
deployment.
Work with Channels and MCP
Configure the CLI
clawdi config paths to identify the local paths used by the current CLI
installation. Do not edit generated or credential files unless a specific
troubleshooting guide tells you to.
For the complete command list, see clawdi --help and the current CLI
reference in the Clawdi
repository.