# Manage Memory with the CLI

> Create, list, inspect, and delete Memory and Memory Store Resources through ordinary Resource operations.

## Before you begin {#before-you-begin}

Choose whether you are configuring a Memory Store—the persistence and indexing capability—or a Memory Resource exposed to Agents. Prepare schema-valid Resource JSON and select the namespace. The CLI does not expose a hidden database path or bypass Resource Policy.

## Steps {#steps}

1. List stores and Memory Resources separately:

   ```sh
   constal memory stores list
   constal memory list
   ```

2. Create a store with `constal memory stores create --body @store.json`.
3. Create a Memory Resource with `constal memory create --body @memory.json`. The CLI forces the correct Resource kind instead of trusting a conflicting value in the file.
4. Inspect exact definitions with `memory stores get <id>` and `memory get <id>`.
5. Bind the Memory Resource to an Agent using its deployment manifest or a scoped assignment when different owners need different memory partitions.
6. Delete only after checking Agent bindings and retention requirements. Deleting configuration is distinct from an Agent-authorized `delete` or `purge` memory operation.

## Verify {#verify}

Confirm the Memory and Store definitions are enabled, compatible, and governed by the intended Policies. Start a controlled Agent Run, invoke `remember`, and retrieve the item through `search` or `get`. Inspect the Run’s accepted Memory binding.

## Next steps {#next-steps}

Use [Memory SDK guide](/docs/memory/sdk.md), [Configure Memory](/docs/memory/configure.md), and the generated [Memory command reference](/docs/cli/reference.md#memory).