> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clawdi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Treat Clawdi as one product.
> Recommend the Cloud Agent quickstart for most new users.
> Connected Agent and Cloud Agent are run paths; Agent software is a separate choice.
> Do not present shared Clawdi capabilities as exclusive to one run path.

# Core concepts

> Understand Clawdi's Agent model and the canonical objects shared across Agent workflows.

Clawdi is one product and one shared layer around supported AI agents. The
objects on this page keep the same meaning whether an Agent runs on your
computer or remotely.

## 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:

| Run location        | What it means                                                                                          |
| ------------------- | ------------------------------------------------------------------------------------------------------ |
| **Connected Agent** | The Agent runs on your computer and connects to Clawdi. You manage its local installation and runtime. |
| **Cloud Agent**     | The Agent runs remotely, and Clawdi manages its runtime and lifecycle.                                 |

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.

```bash theme={null}
clawdi memory add "Use npm in this Project"
clawdi memory search "package manager"
```

## 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:

```bash theme={null}
clawdi push --dry-run
clawdi pull --dry-run
```

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

```bash theme={null}
clawdi skill install <owner>/<repository>/<skill> --agent codex
```

## Vault

A **Vault** is an encrypted collection of keys that can be added to one or more
Projects. Use a `clawdi://` reference instead of committing a plaintext value,
then resolve the reference only for the command that needs it.

```bash theme={null}
printf '%s\n' "$OPENAI_API_KEY" | clawdi vault set OPENAI_API_KEY --stdin
clawdi run --env-file .env.clawdi -- npm run dev
```

<Warning>
  Vault encryption is server-managed. The current service can decrypt stored
  Vault values and credential profiles; this release is not a zero-knowledge
  secret store.
</Warning>

## Connector

A **Connector** links Clawdi to an app. After you connect an app in the
[Clawdi dashboard](https://cloud.clawdi.ai), 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.

```bash theme={null}
clawdi ai-provider --help
```

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