Agent
An Agent is the Clawdi object for an AI agent you add to your account. There are two ways to run and add one:
This run-location choice is separate from Agent software. Claude Code,
Codex, Hermes, OpenClaw, and other supported runtimes name the software the
Agent uses; they do not name where it runs. Supported software and integrations
can differ between the two run paths.
Project
A Project groups the Skills and Vault access an Agent or teammate can use. Attach a Project to an Agent when that Agent should use its resources. Project sharing and access remain explicit.Memory
A Memory is durable account-level context an Agent can recall, such as a preference, fact, or decision. Keep a Memory concise and reusable; do not use it for a complete transcript or secret value.Session
A Session is conversation history produced by an Agent. Clawdi stores or syncs supported Session data so you can review and recall earlier work. For Connected Agents, preview local synchronization before writing data:Skill
A Skill is reusable instruction content an Agent can read from a Project or its supported local Skill directory. For a Connected Agent, the Agent’s guarded local filesystem remains authoritative for its local Skill files. Importing a Project Skill is an explicit action.Vault
A Vault is an encrypted collection of keys that can be added to one or more Projects. Use aclawdi:// reference instead of committing a plaintext value,
then resolve the reference only for the command that needs it.
Connector
A Connector links Clawdi to an app. After you connect an app in the Clawdi dashboard, approved tools can be available to Agents through supported integrations such as MCP. Connector management is in the dashboard, not the CLI.Channel
A Channel is a messaging connection between an external chat and a linked Agent. Some providers use a bot or account for that connection. Channel controls appear only for supported Agent workflows; use the availability shown in the dashboard or current CLI help.AI Provider
An AI Provider records how an Agent reaches a model service, including provider configuration and a credential reference. It is distinct from the Agent software that uses it. For an Agent on your computer, the CLI maintains a local AI Provider catalog. The catalog stores metadata and credential references, not API key values, and model requests continue to go directly from the Agent runtime to the provider. For a Cloud Agent, the AI Providers and model controls in the Clawdi dashboard configure the remote runtime. The local catalog and the Cloud Agent controls are different surfaces for the same canonical concept; do not assume that a setting in one automatically changes the other.Availability
An object’s definition does not change with Agent run location. The actions and integrations shown for an Agent can still vary by run path, Agent software, and current runtime state. Use the controls shown for that Agent and the--help
output shipped with your CLI version.