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

# Memory

> Learn what a fleet can remember between events.

# Memory

## What it is

Memory stores short facts for one fleet. A later run can recall those facts by key or text.

The fleet creates, owns, updates, and removes its memory entries. Workspace members can inspect entries through the dashboard or API. Members with fleet write access can forget entries.

## Why it exists

Memory lets a fleet keep useful conclusions between events. Store conclusions instead of full transcripts.

## How it behaves

| Category       | Use                                        | Retention                       |
| -------------- | ------------------------------------------ | ------------------------------- |
| `core`         | Facts that future runs should keep.        | Until removal or limit eviction |
| `daily`        | Short follow-ups and reminders.            | 72 hours                        |
| `conversation` | Temporary findings from one investigation. | Recent-window selection         |
| Custom         | A named category for your fleet.           | Recent-window selection         |

`memory_store` writes or replaces a stable key. `memory_recall` searches keys and content by substring.

`memory_list` filters entries. `memory_forget` deletes one key.

The dashboard's fleet detail page lists each entry's content, category, and update time. Forgetting an entry requires fleet write access.

The API route is `DELETE /v1/workspaces/{workspace_id}/fleets/{fleet_id}/memories/{key}`. It returns `204` after deletion and `UZ-MEM-004` when the key is absent.

`<FLEET_ID>` comes from `agentsfleet list`.

```bash theme={"theme":"vesper"}
agentsfleet memory list --fleet <FLEET_ID>
```

```text theme={"theme":"vesper"}
KEY          CATEGORY    UPDATED
<varies>     <varies>    <varies>
```

The list is newest first and pages by cursor. `--starting-after <KEY>` resumes after a key an earlier page returned. When more entries remain, the table prints the command that fetches the next page, and `--json` carries `next_cursor` for scripts.

The dashboard's memory panel follows the cursor to the end on its own, so it shows every entry.

## Limits

One fleet can keep 1,000 entries. At the limit, `agentsfleet` removes the oldest non-core entry first.

One entry can contain 16 KiB. One memory update can contain 256 KiB across all changed entries.

`daily` entries older than 72 hours are removed during the fleet's next memory update. Explicitly forgotten entries cannot be recovered.

## Related pages

* [Run context](/concepts/context-lifecycle)
* [Command index](/cli/agentsfleet)
* [Fleet overview](/fleets/overview)