From 3b7b0f348dc2d1d0c3abfeca72cb45c14108ff64 Mon Sep 17 00:00:00 2001 From: Soham Daga Date: Tue, 28 Jul 2026 14:50:53 +0530 Subject: [PATCH] docs(memories): clarify maxForget is query-mode only (id mode ignores it) --- apps/docs/recall/memory-operations.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/docs/recall/memory-operations.mdx b/apps/docs/recall/memory-operations.mdx index fb67af3f..6e58e8e2 100644 --- a/apps/docs/recall/memory-operations.mdx +++ b/apps/docs/recall/memory-operations.mdx @@ -250,7 +250,7 @@ This is a bulk, destructive operation. Always **`dryRun` first** to review what | `containerTag` | string | yes | Container tag / space to scope the operation to | | `dryRun` | boolean | no | When `true`, returns what *would* be forgotten without changing anything. Defaults to `false` | | `threshold` | number | no | Similarity floor (0–1) for candidate memories (`query` mode only). Lower casts a wider net. Defaults to `0.5` | -| `maxForget` | number | no | Safety cap on how many memories may be forgotten in one call (1–500). Defaults to `100` | +| `maxForget` | number | no | Safety cap for **query mode** — the most matches one call may forget (1–500). Defaults to `100`. Ignored in id mode, which forgets exactly the ids you pass (bounded only by the 500-item array limit) | | `reason` | string | no | Reason recorded as `forgetReason` on each forgotten memory | \* Provide either `query` or `ids`.