@mastra/memory 1.6.0 → 1.6.1

package/dist/docs/SKILL.md

@@ -3,7 +3,7 @@ name: mastra-memory
 description: Documentation for @mastra/memory. Use when working with @mastra/memory APIs, configuration, or implementation.
 metadata:
   package: "@mastra/memory"
-  version: "1.6.0"
+  version: "1.6.1"
 ---
 
 ## When to use

package/dist/docs/assets/SOURCE_MAP.json

@@ -1,71 +1,71 @@
 {
-  "version": "1.6.0",
+  "version": "1.6.1",
   "package": "@mastra/memory",
   "exports": {
     "OBSERVATIONAL_MEMORY_DEFAULTS": {
       "types": "dist/processors/index.d.ts",
-      "implementation": "dist/chunk-A62BQK35.js"
+      "implementation": "dist/chunk-GBBQIJQF.js"
     },
     "OBSERVATION_CONTEXT_INSTRUCTIONS": {
       "types": "dist/processors/index.d.ts",
-      "implementation": "dist/chunk-A62BQK35.js"
+      "implementation": "dist/chunk-GBBQIJQF.js"
     },
     "OBSERVATION_CONTEXT_PROMPT": {
       "types": "dist/processors/index.d.ts",
-      "implementation": "dist/chunk-A62BQK35.js"
+      "implementation": "dist/chunk-GBBQIJQF.js"
     },
     "OBSERVATION_CONTINUATION_HINT": {
       "types": "dist/processors/index.d.ts",
-      "implementation": "dist/chunk-A62BQK35.js"
+      "implementation": "dist/chunk-GBBQIJQF.js"
     },
     "OBSERVER_SYSTEM_PROMPT": {
       "types": "dist/processors/index.d.ts",
-      "implementation": "dist/chunk-A62BQK35.js"
+      "implementation": "dist/chunk-GBBQIJQF.js"
     },
     "ObservationalMemory": {
       "types": "dist/processors/index.d.ts",
-      "implementation": "dist/chunk-A62BQK35.js",
-      "line": 1258
+      "implementation": "dist/chunk-GBBQIJQF.js",
+      "line": 1642
     },
     "TokenCounter": {
       "types": "dist/processors/index.d.ts",
-      "implementation": "dist/chunk-A62BQK35.js",
-      "line": 919
+      "implementation": "dist/chunk-GBBQIJQF.js",
+      "line": 1401
     },
     "buildObserverPrompt": {
       "types": "dist/processors/index.d.ts",
-      "implementation": "dist/chunk-A62BQK35.js",
-      "line": 533
+      "implementation": "dist/chunk-GBBQIJQF.js",
+      "line": 822
     },
     "buildObserverSystemPrompt": {
       "types": "dist/processors/index.d.ts",
-      "implementation": "dist/chunk-A62BQK35.js",
-      "line": 281
+      "implementation": "dist/chunk-GBBQIJQF.js",
+      "line": 570
     },
     "extractCurrentTask": {
       "types": "dist/processors/index.d.ts",
-      "implementation": "dist/chunk-A62BQK35.js",
-      "line": 662
+      "implementation": "dist/chunk-GBBQIJQF.js",
+      "line": 951
     },
     "formatMessagesForObserver": {
       "types": "dist/processors/index.d.ts",
-      "implementation": "dist/chunk-A62BQK35.js",
-      "line": 376
+      "implementation": "dist/chunk-GBBQIJQF.js",
+      "line": 665
     },
     "hasCurrentTaskSection": {
       "types": "dist/processors/index.d.ts",
-      "implementation": "dist/chunk-A62BQK35.js",
-      "line": 650
+      "implementation": "dist/chunk-GBBQIJQF.js",
+      "line": 939
     },
     "optimizeObservationsForContext": {
       "types": "dist/processors/index.d.ts",
-      "implementation": "dist/chunk-A62BQK35.js",
-      "line": 673
+      "implementation": "dist/chunk-GBBQIJQF.js",
+      "line": 962
     },
     "parseObserverOutput": {
       "types": "dist/processors/index.d.ts",
-      "implementation": "dist/chunk-A62BQK35.js",
-      "line": 564
+      "implementation": "dist/chunk-GBBQIJQF.js",
+      "line": 853
     },
     "extractWorkingMemoryContent": {
       "types": "dist/index.d.ts",
@@ -96,7 +96,7 @@
     "processors": {
       "index": "dist/processors/index.js",
       "chunks": [
-        "chunk-A62BQK35.js"
+        "chunk-GBBQIJQF.js"
       ]
     }
   }

package/dist/docs/references/docs-agents-agent-approval.md

@@ -1,10 +1,29 @@
-# Agent Approval
+# Agent approval
 
-Agents sometimes require the same [human-in-the-loop](https://mastra.ai/docs/workflows/human-in-the-loop) oversight used in workflows when calling tools that handle sensitive operations, like deleting resources or performing running long processes. With agent approval you can suspend a tool call and provide feedback to the user, or approve or decline a tool call based on targeted application conditions.
+Agents sometimes require the same [human-in-the-loop](https://mastra.ai/docs/workflows/human-in-the-loop) oversight used in workflows when calling tools that handle sensitive operations, like deleting resources or running long processes. With agent approval you can suspend a tool call before it executes so a human can approve or decline it, or let tools suspend themselves to request additional context from the user.
 
-## Tool call approval
+## How approval works
 
-Tool call approval can be enabled at the agent level and apply to every tool the agent uses, or at the tool level providing more granular control over individual tool calls.
+Mastra offers two distinct mechanisms for pausing tool calls: **pre-execution approval** and **runtime suspension**.
+
+### Pre-execution approval
+
+Pre-execution approval pauses a tool call _before_ its `execute` function runs. The LLM still decides which tool to call and provides arguments, but `execute` doesn't run until you explicitly approve.
+
+Two flags control this, combined with OR logic. If _either_ is `true`, the call pauses:
+
+| Flag                        | Where to set it                   | Scope                                       |
+| --------------------------- | --------------------------------- | ------------------------------------------- |
+| `requireToolApproval: true` | `stream()` / `generate()` options | Pauses **every** tool call for that request |
+| `requireApproval: true`     | `createTool()` definition         | Pauses calls to **that specific tool**      |
+
+The stream emits a `tool-call-approval` chunk when a call is paused this way. You then call `approveToolCall()` or `declineToolCall()` to continue.
+
+### Runtime suspension with `suspend()`
+
+A tool can also pause _during_ its `execute` function by calling `suspend()`. This is useful when the tool starts running and then discovers it needs additional user input or confirmation before it can finish.
+
+The stream emits a `tool-call-suspended` chunk with a custom payload defined by the tool's `suspendSchema`. You resume by calling `resumeStream()` with data matching the tool's `resumeSchema`.
 
 ### Storage
 
@@ -24,7 +43,7 @@ export const mastra = new Mastra({
 
 ## Agent-level approval
 
-When calling an agent using `.stream()` set `requireToolApproval` to `true` which will prevent the agent from calling any of the tools defined in its configuration.
+Pass `requireToolApproval: true` to `stream()` or `generate()` to pause every tool call before execution. The LLM still decides which tools to call and with what arguments but no tool runs until you approve or decline.
 
 ```typescript
 const stream = await agent.stream("What's the weather in London?", {
@@ -32,9 +51,20 @@ const stream = await agent.stream("What's the weather in London?", {
 })
 ```
 
+When a tool call is paused, the stream emits a `tool-call-approval` chunk containing the `toolCallId`, `toolName`, and `args`. Use this to inspect the pending call and decide whether to approve or decline:
+
+```typescript
+for await (const chunk of stream.fullStream) {
+  if (chunk.type === 'tool-call-approval') {
+    console.log('Tool:', chunk.payload.toolName)
+    console.log('Args:', chunk.payload.args)
+  }
+}
+```
+
 ### Approving tool calls
 
-To approve a tool call, access `approveToolCall` from the `agent`, passing in the `runId` of the stream. This will let the agent know its now OK to call its tools.
+Call `approveToolCall()` on the agent with the `runId` of the stream to resume the suspended tool call and let it execute:
 
 ```typescript
 const handleApproval = async () => {
@@ -49,7 +79,7 @@ const handleApproval = async () => {
 
 ### Declining tool calls
 
-To decline a tool call, access the `declineToolCall` from the `agent`. You will see the streamed response from the agent, but it won't call its tools.
+Call `declineToolCall()` on the agent to skip the tool call. The agent continues without executing the tool and responds accordingly:
 
 ```typescript
 const handleDecline = async () => {
@@ -64,19 +94,19 @@ const handleDecline = async () => {
 
 ## Tool approval with generate()
 
-Tool approval also works with the `generate()` method for non-streaming use cases. When using `generate()` with `requireToolApproval: true`, the method returns immediately when a tool requires approval instead of executing it.
+Tool approval also works with the `generate()` method for non-streaming use cases. When a tool requires approval during a `generate()` call, the method returns immediately instead of executing the tool.
 
 ### How it works
 
 When a tool requires approval during a `generate()` call, the response includes:
 
-- `finishReason: 'suspended'` - indicates the agent is waiting for approval
-- `suspendPayload` - contains tool call details (`toolCallId`, `toolName`, `args`)
-- `runId` - needed to approve or decline the tool call
+- `finishReason: 'suspended'`: Indicates the agent is waiting for approval
+- `suspendPayload`: Contains tool call details (`toolCallId`, `toolName`, `args`)
+- `runId`: Needed to approve or decline the tool call
 
 ### Approving tool calls
 
-To approve a tool call with `generate()`, use the `approveToolCallGenerate` method:
+Use `approveToolCallGenerate()` to approve the tool call and get the final result:
 
 ```typescript
 const output = await agent.generate('Find user John', {
@@ -99,7 +129,7 @@ if (output.finishReason === 'suspended') {
 
 ### Declining tool calls
 
-To decline a tool call, use the `declineToolCallGenerate` method:
+Use `declineToolCallGenerate()` to skip the tool call:
 
 ```typescript
 if (output.finishReason === 'suspended') {
@@ -108,12 +138,12 @@ if (output.finishReason === 'suspended') {
     toolCallId: output.suspendPayload.toolCallId,
   })
 
-  // Agent will respond acknowledging the declined tool
+  // Agent responds acknowledging the declined tool
   console.log(result.text)
 }
 ```
 
-### Stream vs Generate comparison
+### Stream vs generate comparison
 
 | Aspect             | `stream()`                   | `generate()`                                     |
 | ------------------ | ---------------------------- | ------------------------------------------------ |
@@ -125,11 +155,11 @@ if (output.finishReason === 'suspended') {
 
 ## Tool-level approval
 
-There are two types of tool call approval. The first uses `requireApproval`, which is a property on the tool definition, while `requireToolApproval` is a parameter passed to `agent.stream()`. The second uses `suspend` and lets the agent provide context or confirmation prompts so the user can decide whether the tool call should continue.
+Instead of pausing every tool call at the agent level, you can mark individual tools as requiring approval. This gives you granular control — only specific tools pause, while others execute immediately.
 
-### Tool approval using `requireToolApproval`
+### Approval using `requireApproval`
 
-In this approach, `requireApproval` is configured on the tool definition (shown below) rather than on the agent.
+Set `requireApproval: true` on a tool definition. The tool pauses before execution regardless of whether `requireToolApproval` is set on the agent:
 
 ```typescript
 export const testTool = createTool({
@@ -154,30 +184,30 @@ export const testTool = createTool({
 })
 ```
 
-When `requireApproval` is true for a tool, the stream will include chunks of type `tool-call-approval` to indicate that the call is paused. To continue the call, invoke `resumeStream` with the required `resumeSchema` and the `runId`.
+When `requireApproval` is `true`, the stream emits `tool-call-approval` chunks the same way agent-level approval does. Use `approveToolCall()` or `declineToolCall()` to continue:
 
 ```typescript
 const stream = await agent.stream("What's the weather in London?")
 
 for await (const chunk of stream.fullStream) {
   if (chunk.type === 'tool-call-approval') {
-    console.log('Approval required.')
+    console.log('Approval required for:', chunk.payload.toolName)
   }
 }
 
-const handleResume = async () => {
-  const resumedStream = await agent.resumeStream({ approved: true }, { runId: stream.runId })
+const handleApproval = async () => {
+  const approvedStream = await agent.approveToolCall({ runId: stream.runId })
 
-  for await (const chunk of resumedStream.textStream) {
+  for await (const chunk of approvedStream.textStream) {
     process.stdout.write(chunk)
   }
   process.stdout.write('\n')
 }
 ```
 
-### Tool approval using `suspend`
+### Approval using `suspend`
 
-With this approach, neither the agent nor the tool uses `requireApproval`. Instead, the tool implementation calls `suspend` to pause execution and return context or confirmation prompts to the user.
+With this approach, neither the agent nor the tool uses `requireApproval`. Instead, the tool's `execute` function calls `suspend` to pause at a specific point and return context or confirmation prompts to the user. This is useful when approval depends on runtime conditions rather than being unconditional.
 
 ```typescript
 export const testToolB = createTool({
@@ -210,7 +240,7 @@ export const testToolB = createTool({
 })
 ```
 
-With this approach the stream will include a `tool-call-suspended` chunk, and the `suspendPayload` will contain the `reason` defined by the tool's `suspendSchema`. To continue the call, invoke `resumeStream` with the required `resumeSchema` and the `runId`.
+With this approach the stream includes a `tool-call-suspended` chunk, and the `suspendPayload` contains the `reason` defined by the tool's `suspendSchema`. Call `resumeStream` with the `resumeSchema` data and `runId` to continue:
 
 ```typescript
 const stream = await agent.stream("What's the weather in London?")
@@ -349,7 +379,7 @@ User: "San Francisco"
 Agent: "The weather in San Francisco is: San Francisco: ☀️ +72°F"
 ```
 
-The second message automatically resumes the suspended tool - the agent extracts `{ city: "San Francisco" }` from the user's message and passes it as `resumeData`.
+The second message automatically resumes the suspended tool, the agent extracts `{ city: "San Francisco" }` from the user's message and passes it as `resumeData`.
 
 ### Requirements
 
@@ -370,7 +400,7 @@ Both approaches work with the same tool definitions. Automatic resumption trigge
 
 ## Tool approval: Supervisor pattern
 
-The [supervisor pattern](https://mastra.ai/docs/agents/networks) lets a supervisor agent coordinate multiple subagents using `.stream()` or `.generate()`. The supervisor delegates tasks to subagents, which may use tools that require approval. When this happens, tool approvals properly propagate through the delegation chain -- the approval request surfaces at the supervisor level where you can handle it, regardless of which subagent triggered it.
+The [supervisor pattern](https://mastra.ai/docs/agents/networks) lets a supervisor agent coordinate multiple subagents using `.stream()` or `.generate()`. The supervisor delegates tasks to subagents, which may use tools that require approval. When this happens, tool approvals properly propagate through the delegation chain — the approval request surfaces at the supervisor level where you can handle it, regardless of which subagent triggered it.
 
 ### How it works
 
@@ -453,7 +483,7 @@ for await (const chunk of stream.fullStream) {
 
 ### Declining tool calls in supervisor pattern
 
-You can also decline tool calls at the supervisor level by calling `declineToolCall`. The supervisor will respond acknowledging the declined tool without executing it:
+Decline tool calls at the supervisor level by calling `declineToolCall`. The supervisor responds acknowledging the declined tool without executing it:
 
 ```typescript
 for await (const chunk of stream.fullStream) {
@@ -466,7 +496,7 @@ for await (const chunk of stream.fullStream) {
       toolCallId: chunk.payload.toolCallId,
     })
 
-    // The supervisor will respond acknowledging the declined tool
+    // The supervisor responds acknowledging the declined tool
     for await (const declineChunk of declineStream.textStream) {
       process.stdout.write(declineChunk)
     }
@@ -476,7 +506,7 @@ for await (const chunk of stream.fullStream) {
 
 ### Using suspend() in supervisor pattern
 
-Tools can also use [`suspend()`](#tool-approval-using-suspend) to pause execution and return context to the user. This approach works through the supervisor delegation chain the same way `requireApproval` does -- the suspension surfaces at the supervisor level:
+Tools can also use [`suspend()`](#approval-using-suspend) to pause execution and return context to the user. This approach works through the supervisor delegation chain the same way `requireApproval` does — the suspension surfaces at the supervisor level:
 
 ```typescript
 const conditionalTool = createTool({

package/dist/docs/references/docs-agents-supervisor-agents.md

@@ -192,7 +192,7 @@ const stream = await supervisor.stream('Research AI trends', {
 })
 ```
 
-Return `{ continue: true }` to keep iterating, or `{ continue: false }` to stop. Include optional `feedback` to add guidance that's visible to the next iteration.
+Return `{ continue: true }` to keep iterating, or `{ continue: false }` to stop. Include optional `feedback` to inject guidance into the conversation. When `feedback` is combined with `continue: false`, the model may get one final turn to produce a text response incorporating the feedback, but only if the current iteration is still active (e.g., after tool calls) — otherwise no extra turn is granted.
 
 ## Memory isolation
 

package/dist/docs/references/docs-memory-observational-memory.md

@@ -170,6 +170,15 @@ const memory = new Memory({
 })
 ```
 
+### Token counting cache
+
+OM caches tiktoken part estimates in message metadata to reduce repeat counting work during threshold checks and buffering decisions.
+
+- Per-part estimates are stored on `part.providerMetadata.mastra` and reused on subsequent passes when the cache version/tokenizer source matches.
+- For string-only message content (without parts), OM uses a message-level metadata fallback cache.
+- Message and conversation overhead are still recalculated on every pass. The cache only stores payload estimates, so counting semantics stay the same.
+- `data-*` and `reasoning` parts are still skipped and are not cached.
+
 ## Async Buffering
 
 Without async buffering, the Observer runs synchronously when the message threshold is reached — the agent pauses mid-conversation while the Observer LLM call completes. With async buffering (enabled by default), observations are pre-computed in the background as the conversation grows. When the threshold is hit, buffered observations activate instantly with no pause.

package/dist/docs/references/docs-memory-semantic-recall.md

@@ -147,8 +147,24 @@ Supported embedding models:
 
 - **OpenAI**: `text-embedding-3-small`, `text-embedding-3-large`, `text-embedding-ada-002`
 - **Google**: `gemini-embedding-001`
+- **OpenRouter**: Access embedding models from various providers
 
-The model router automatically handles API key detection from environment variables (`OPENAI_API_KEY`, `GOOGLE_GENERATIVE_AI_API_KEY`).
+```ts
+import { Agent } from '@mastra/core/agent'
+import { Memory } from '@mastra/memory'
+import { ModelRouterEmbeddingModel } from '@mastra/core/llm'
+
+const agent = new Agent({
+  memory: new Memory({
+    embedder: new ModelRouterEmbeddingModel({
+      providerId: 'openrouter',
+      modelId: 'openai/text-embedding-3-small',
+    }),
+  }),
+})
+```
+
+The model router automatically handles API key detection from environment variables (`OPENAI_API_KEY`, `GOOGLE_GENERATIVE_AI_API_KEY`, `OPENROUTER_API_KEY`).
 
 ### Using AI SDK Packages
 

package/dist/docs/references/reference-core-getMemory.md

@@ -16,11 +16,11 @@ const thread = await memory.createThread({
 
 ## Parameters
 
-**key:** (`TMemoryKey extends keyof TMemory`): The registry key of the memory instance to retrieve. Must match a key used when registering memory in the Mastra constructor.
+**key** (`TMemoryKey extends keyof TMemory`): The registry key of the memory instance to retrieve. Must match a key used when registering memory in the Mastra constructor.
 
 ## Returns
 
-**memory:** (`TMemory[TMemoryKey]`): The memory instance with the specified key. Throws an error if the memory is not found.
+**memory** (`TMemory[TMemoryKey]`): The memory instance with the specified key. Throws an error if the memory is not found.
 
 ## Example: Registering and Retrieving Memory
 

package/dist/docs/references/reference-core-listMemory.md

@@ -18,7 +18,7 @@ This method takes no parameters.
 
 ## Returns
 
-**memory:** (`Record<string, MastraMemory>`): An object containing all registered memory instances, keyed by their registry keys.
+**memory** (`Record<string, MastraMemory>`): An object containing all registered memory instances, keyed by their registry keys.
 
 ## Example: Checking Registered Memory
 

package/dist/docs/references/reference-memory-clone-utilities.md

@@ -14,7 +14,7 @@ const isClonedThread = memory.isClone(thread)
 
 ### Parameters
 
-**thread:** (`StorageThreadType`): The thread object to check.
+**thread** (`StorageThreadType`): The thread object to check.
 
 ### Example
 
@@ -40,7 +40,7 @@ const metadata = memory.getCloneMetadata(thread)
 
 ### Parameters
 
-**thread:** (`StorageThreadType`): The thread object to extract clone metadata from.
+**thread** (`StorageThreadType`): The thread object to extract clone metadata from.
 
 ### Example
 
@@ -66,7 +66,7 @@ const sourceThread = await memory.getSourceThread(threadId)
 
 ### Parameters
 
-**threadId:** (`string`): The ID of the cloned thread.
+**threadId** (`string`): The ID of the cloned thread.
 
 ### Example
 
@@ -91,7 +91,7 @@ const clones = await memory.listClones(sourceThreadId)
 
 ### Parameters
 
-**sourceThreadId:** (`string`): The ID of the source thread to find clones for.
+**sourceThreadId** (`string`): The ID of the source thread to find clones for.
 
 ### Example
 
@@ -116,7 +116,7 @@ const history = await memory.getCloneHistory(threadId)
 
 ### Parameters
 
-**threadId:** (`string`): The ID of the thread to get clone history for.
+**threadId** (`string`): The ID of the thread to get clone history for.
 
 ### Example
 

package/dist/docs/references/reference-memory-cloneThread.md

@@ -12,49 +12,45 @@ const { thread, clonedMessages } = await memory.cloneThread({
 
 ## Parameters
 
-**sourceThreadId:** (`string`): The ID of the thread to clone
+**sourceThreadId** (`string`): The ID of the thread to clone
 
-**newThreadId?:** (`string`): Optional custom ID for the cloned thread. If not provided, one will be generated.
+**newThreadId** (`string`): Optional custom ID for the cloned thread. If not provided, one will be generated.
 
-**resourceId?:** (`string`): Optional resource ID for the cloned thread. Defaults to the source thread's resourceId.
+**resourceId** (`string`): Optional resource ID for the cloned thread. Defaults to the source thread's resourceId.
 
-**title?:** (`string`): Optional title for the cloned thread. Defaults to '\[source title] (Copy)'.
+**title** (`string`): Optional title for the cloned thread. Defaults to '\[source title] (Copy)'.
 
-**metadata?:** (`Record<string, unknown>`): Optional metadata to merge with the source thread's metadata. Clone metadata is automatically added.
+**metadata** (`Record<string, unknown>`): Optional metadata to merge with the source thread's metadata. Clone metadata is automatically added.
 
-**options?:** (`CloneOptions`): Optional filtering options for the clone operation.
+**options** (`CloneOptions`): Optional filtering options for the clone operation.
 
-### Options Parameters
+**options.messageLimit** (`number`): Maximum number of messages to clone. When set, clones the most recent N messages.
 
-**messageLimit?:** (`number`): Maximum number of messages to clone. When set, clones the most recent N messages.
+**options.messageFilter** (`MessageFilter`): Filter criteria for selecting which messages to clone.
 
-**messageFilter?:** (`MessageFilter`): Filter criteria for selecting which messages to clone.
+**options.messageFilter.startDate** (`Date`): Only clone messages created on or after this date.
 
-### MessageFilter Parameters
+**options.messageFilter.endDate** (`Date`): Only clone messages created on or before this date.
 
-**startDate?:** (`Date`): Only clone messages created on or after this date.
-
-**endDate?:** (`Date`): Only clone messages created on or before this date.
-
-**messageIds?:** (`string[]`): Only clone messages with these specific IDs.
+**options.messageFilter.messageIds** (`string[]`): Only clone messages with these specific IDs.
 
 ## Returns
 
-**thread:** (`StorageThreadType`): The newly created cloned thread with clone metadata.
+**thread** (`StorageThreadType`): The newly created cloned thread with clone metadata.
 
-**clonedMessages:** (`MastraDBMessage[]`): Array of the cloned messages with new IDs assigned to the new thread.
+**clonedMessages** (`MastraDBMessage[]`): Array of the cloned messages with new IDs assigned to the new thread.
 
-**messageIdMap?:** (`Record<string, string>`): A mapping from source message IDs to their corresponding cloned message IDs.
+**messageIdMap** (`Record<string, string>`): A mapping from source message IDs to their corresponding cloned message IDs.
 
 ### Clone Metadata
 
 The cloned thread's metadata includes a `clone` property with:
 
-**sourceThreadId:** (`string`): The ID of the original thread that was cloned.
+**sourceThreadId** (`string`): The ID of the original thread that was cloned.
 
-**clonedAt:** (`Date`): Timestamp when the clone was created.
+**clonedAt** (`Date`): Timestamp when the clone was created.
 
-**lastMessageId?:** (`string`): The ID of the last message in the source thread at the time of cloning.
+**lastMessageId** (`string`): The ID of the last message in the source thread at the time of cloning.
 
 ## Extended Usage Example
 

package/dist/docs/references/reference-memory-createThread.md

@@ -10,27 +10,27 @@ await memory?.createThread({ resourceId: 'user-123' })
 
 ## Parameters
 
-**resourceId:** (`string`): Identifier for the resource this thread belongs to (e.g., user ID, project ID)
+**resourceId** (`string`): Identifier for the resource this thread belongs to (e.g., user ID, project ID)
 
-**threadId?:** (`string`): Optional custom ID for the thread. If not provided, one will be generated.
+**threadId** (`string`): Optional custom ID for the thread. If not provided, one will be generated.
 
-**title?:** (`string`): Optional title for the thread
+**title** (`string`): Optional title for the thread
 
-**metadata?:** (`Record<string, unknown>`): Optional metadata to associate with the thread
+**metadata** (`Record<string, unknown>`): Optional metadata to associate with the thread
 
 ## Returns
 
-**id:** (`string`): Unique identifier of the created thread
+**id** (`string`): Unique identifier of the created thread
 
-**resourceId:** (`string`): Resource ID associated with the thread
+**resourceId** (`string`): Resource ID associated with the thread
 
-**title:** (`string`): Title of the thread (if provided)
+**title** (`string`): Title of the thread (if provided)
 
-**createdAt:** (`Date`): Timestamp when the thread was created
+**createdAt** (`Date`): Timestamp when the thread was created
 
-**updatedAt:** (`Date`): Timestamp when the thread was last updated
+**updatedAt** (`Date`): Timestamp when the thread was last updated
 
-**metadata:** (`Record<string, unknown>`): Additional metadata associated with the thread
+**metadata** (`Record<string, unknown>`): Additional metadata associated with the thread
 
 ## Extended usage example
 

package/dist/docs/references/reference-memory-getThreadById.md

@@ -10,11 +10,11 @@ await memory?.getThreadById({ threadId: 'thread-123' })
 
 ## Parameters
 
-**threadId:** (`string`): The ID of the thread to be retrieved.
+**threadId** (`string`): The ID of the thread to be retrieved.
 
 ## Returns
 
-**thread:** (`Promise<StorageThreadType | null>`): A promise that resolves to the thread associated with the given ID, or null if not found.
+**thread** (`Promise<StorageThreadType | null>`): A promise that resolves to the thread associated with the given ID, or null if not found.
 
 ### Related
 

package/dist/docs/references/reference-memory-listThreads.md

@@ -61,17 +61,17 @@ const result = await memory.listThreads({
 
 ## Parameters
 
-**filter?:** (`{ resourceId?: string; metadata?: Record<string, unknown> }`): Optional filter object. resourceId filters threads by resource ID. metadata filters threads by metadata key-value pairs (AND logic - all must match)
+**filter** (`{ resourceId?: string; metadata?: Record<string, unknown> }`): Optional filter object. resourceId filters threads by resource ID. metadata filters threads by metadata key-value pairs (AND logic - all must match)
 
-**page?:** (`number`): Page number (0-indexed) to retrieve
+**page** (`number`): Page number (0-indexed) to retrieve
 
-**perPage?:** (`number | false`): Maximum number of threads to return per page, or false to fetch all
+**perPage** (`number | false`): Maximum number of threads to return per page, or false to fetch all
 
-**orderBy?:** (`{ field: 'createdAt' | 'updatedAt', direction: 'ASC' | 'DESC' }`): Sort configuration with field and direction (defaults to { field: 'createdAt', direction: 'DESC' })
+**orderBy** (`{ field: 'createdAt' | 'updatedAt', direction: 'ASC' | 'DESC' }`): Sort configuration with field and direction (defaults to { field: 'createdAt', direction: 'DESC' })
 
 ## Returns
 
-**result:** (`Promise<StorageListThreadsOutput>`): A promise that resolves to paginated thread results with metadata
+**result** (`Promise<StorageListThreadsOutput>`): A promise that resolves to paginated thread results with metadata
 
 The return object contains: