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

# Memories

> Save durable personal context, find it across Agents, and remove information that is no longer true.

A Memory is durable, account-level context. It can be recalled across Agents
and runs, but it is not shared through Projects. See [Core
concepts](/concepts/core-concepts#memory) for the canonical definition.

## Write a useful Memory

Keep one reusable fact, preference, pattern, decision, or piece of context in
each Memory. Include the subject instead of relying on the current
conversation.

```bash theme={null}
clawdi memory search "pull request summaries"
clawdi memory add "For pull requests, I prefer a short summary followed by verification results" --category preference
clawdi memory search "pull request summaries"
```

Valid categories are `fact`, `preference`, `pattern`, `decision`, and
`context`. If you omit `--category`, the CLI uses `fact`.

<Check>
  The search returns the new Memory. A supported Agent with working Clawdi
  tools can recall it in later conversations.
</Check>

<Warning>
  Never store passwords, API keys, private keys, tokens, or connection strings
  as Memories. Clawdi blocks likely secrets at this boundary; store them in a
  [Vault](/guides/vaults-and-secrets) instead.
</Warning>

## Add and find Memories in the dashboard

Open **Memories** in the [Clawdi dashboard](https://cloud.clawdi.ai):

1. Choose **New memory**.
2. Enter concise content and select a category.
3. Save it, then use search or a category filter to find it again.

Open a Memory to inspect its source, creation time, and recall count when that
information is available.

## Extract Memories from a Session

First make sure the supported Session is synced, then identify its local
Session ID:

```bash theme={null}
clawdi push --modules sessions --dry-run
clawdi push --modules sessions
clawdi session list --limit 10
clawdi session extract <session-id>
```

Extraction asks the service's configured model to create Memories from that
Session. Some deployments do not configure a memory-extraction model; in that
case the CLI reports that extraction is unavailable and makes no Memories.

Review extracted Memories in the dashboard and delete anything too broad,
duplicated, sensitive, or no longer accurate.

## Delete outdated context

The shortest path is the delete action on the Memory card or detail page. For
the CLI, obtain the full ID from JSON output and remove that exact record:

```bash theme={null}
clawdi memory list --json
clawdi memory rm <full-memory-id>
```

Deletion removes the Memory from future recall. If the underlying preference
or decision changed, add a new, explicit Memory after removing the obsolete
one.

If an Agent cannot recall a known Memory, verify its Clawdi tools with
[Connectors and MCP](/guides/connectors-and-mcp) and see the [MCP
troubleshooting steps](/troubleshooting#mcp-tools-are-missing-or-stale).
Run `clawdi memory --help` for the command surface shipped with your CLI.