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

# memory

# `wednesdayai memory`

Manage semantic memory indexing and search.
Provided by the active memory plugin (default: `memory-core`; set `plugins.slots.memory = "none"` to disable).

Related:

* Memory concept: [Memory](https://docs.wednesdayai.dev/next/developers/concepts/memory.md)
* Plugins: [Plugins](https://docs.wednesdayai.dev/next/users/tools/plugin.md)

## Examples

```bash theme={"dark"}
wednesdayai memory status
wednesdayai memory status --deep
wednesdayai memory status --deep --index
wednesdayai memory status --deep --index --verbose
wednesdayai memory index
wednesdayai memory index --verbose
wednesdayai memory search "release checklist"
wednesdayai memory search --query "release checklist"
wednesdayai memory status --agent main
wednesdayai memory index --agent main --verbose
```

## Options

Common:

* `--agent <id>`: scope to a single agent (default: all configured agents).
* `--verbose`: emit detailed logs during probes and indexing.

`memory search`:

* Query input: pass either positional `[query]` or `--query <text>`.
* If both are provided, `--query` wins.
* If neither is provided, the command exits with an error.
* The command runs without session identity, so `memory.qmd.scope` rules that match on `channel`
  or `chatType` cannot apply and the scope default governs. On the active QMD backend, a denial
  is reported as an error and the command exits 1 instead of returning empty results; with the
  default DM-only scope this denies the CLI search entirely — set
  `memory.qmd.scope.default: "allow"` to permit identity-less CLI search. A builtin fallback
  backend does not enforce the scope.

Notes:

* `memory status --deep` probes vector + embedding availability.
* `memory status --deep --index` runs a reindex if the store is dirty.
* `memory index --verbose` prints per-phase details (provider, model, sources, batch activity).
* `memory status` includes any extra paths configured via `memorySearch.extraPaths`.
* If effectively active memory remote API key fields are configured as SecretRefs, the command resolves those values from the active gateway snapshot. If gateway is unavailable, the command fails fast.
* Gateway version skew note: this command path requires a gateway that supports `secrets.resolve`; older gateways return an unknown-method error.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.