@mastra/memory 1.0.0 → 1.0.1-alpha.0

package/dist/docs/agents/01-agent-memory.md

@@ -15,12 +15,12 @@ Use memory when your agent needs to maintain multi-turn conversations that refer
 To enable memory in Mastra, install the `@mastra/memory` package along with a storage provider.
 
 ```bash npm2yarn
-npm install @mastra/memory@beta @mastra/libsql@beta
+npm install @mastra/memory@latest @mastra/libsql@latest
 ```
 
 ## Storage providers
 
-Memory requires a storage provider to persist message history, including user messages and agent responses. For more details on available providers and how storage works in Mastra, see the [Storage](https://mastra.ai/docs/v1/memory/storage) documentation.
+Memory requires a storage provider to persist message history, including user messages and agent responses. For more details on available providers and how storage works in Mastra, see the [Storage](https://mastra.ai/docs/memory/storage) documentation.
 
 ## Configuring memory
 
@@ -45,7 +45,7 @@ export const memoryAgent = new Agent({
 
 > **Note:**
 
-Visit [Memory Class](https://mastra.ai/reference/v1/memory/memory-class) for a full list of configuration options.
+Visit [Memory Class](https://mastra.ai/reference/memory/memory-class) for a full list of configuration options.
 
   
 
@@ -67,7 +67,7 @@ export const mastra = new Mastra({
 
 > **Note:**
 
-Visit [libSQL Storage](https://mastra.ai/reference/v1/storage/libsql) for a full list of configuration options.
+Visit [libSQL Storage](https://mastra.ai/reference/storage/libsql) for a full list of configuration options.
 
   
 
@@ -91,7 +91,7 @@ export const memoryAgent = new Agent({
 ```
 
 > **Mastra Cloud Store limitation**
-Agent-level storage is not supported when using [Mastra Cloud Store](https://mastra.ai/docs/v1/mastra-cloud/deployment#using-mastra-cloud-store). If you use Mastra Cloud Store, configure storage on the Mastra instance instead. This limitation does not apply if you bring your own database.
+Agent-level storage is not supported when using [Mastra Cloud Store](https://mastra.ai/docs/mastra-cloud/deployment#using-mastra-cloud-store). If you use Mastra Cloud Store, configure storage on the Mastra instance instead. This limitation does not apply if you bring your own database.
 
 ## Message history
 
@@ -132,7 +132,7 @@ To learn more about memory see the [Memory](../memory/overview) documentation.
 
 ## Using `RequestContext`
 
-Use [RequestContext](https://mastra.ai/docs/v1/server/request-context) to access request-specific values. This lets you conditionally select different memory or storage configurations based on the context of the request.
+Use [RequestContext](https://mastra.ai/docs/server/request-context) to access request-specific values. This lets you conditionally select different memory or storage configurations based on the context of the request.
 
 ```typescript title="src/mastra/agents/memory-agent.ts"
 export type UserTier = {
@@ -156,11 +156,11 @@ export const memoryAgent = new Agent({
 
 > **Note:**
 
-Visit [Request Context](https://mastra.ai/docs/v1/server/request-context) for more information.
+Visit [Request Context](https://mastra.ai/docs/server/request-context) for more information.
 
 ## Related
 
 - [Working Memory](../memory/working-memory)
 - [Semantic Recall](../memory/semantic-recall)
 - [Storage](../memory/storage)
-- [Request Context](https://mastra.ai/docs/v1/server/request-context)
+- [Request Context](https://mastra.ai/docs/server/request-context)

package/dist/docs/agents/02-networks.md

@@ -288,5 +288,5 @@ const final = await stream.object;
 
 - [Agent Memory](./agent-memory)
 - [Workflows Overview](../workflows/overview)
-- [Request Context](https://mastra.ai/docs/v1/server/request-context)
+- [Request Context](https://mastra.ai/docs/server/request-context)
 - [Supervisor example](https://github.com/mastra-ai/mastra/tree/main/examples/supervisor-agent)

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

@@ -2,7 +2,7 @@
 
 # Agent Approval
 
-Agents sometimes require the same [human-in-the-loop](https://mastra.ai/docs/v1/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 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.
 
 ## Tool call approval
 
@@ -374,4 +374,4 @@ Both approaches work with the same tool definitions. Automatic resumption trigge
 - [Agent Overview](./overview)
 - [Tools Overview](../mcp/overview)
 - [Agent Memory](./agent-memory)
-- [Request Context](https://mastra.ai/docs/v1/server/request-context)
+- [Request Context](https://mastra.ai/docs/server/request-context)

package/dist/docs/agents/04-network-approval.md

@@ -2,7 +2,7 @@
 
 # Network Approval
 
-Agent networks can require the same [human-in-the-loop](https://mastra.ai/docs/v1/workflows/human-in-the-loop) oversight used in individual agents and workflows. When a tool, sub-agent, or workflow within a network requires approval or suspends execution, the network pauses and emits events that allow your application to collect user input before resuming.
+Agent networks can require the same [human-in-the-loop](https://mastra.ai/docs/workflows/human-in-the-loop) oversight used in individual agents and workflows. When a tool, sub-agent, or workflow within a network requires approval or suspends execution, the network pauses and emits events that allow your application to collect user input before resuming.
 
 ## Storage
 
@@ -270,5 +270,5 @@ Both approaches work with the same tool definitions. Automatic resumption trigge
 
 - [Agent Networks](./networks)
 - [Agent Approval](./agent-approval)
-- [Human-in-the-Loop](https://mastra.ai/docs/v1/workflows/human-in-the-loop)
+- [Human-in-the-Loop](https://mastra.ai/docs/workflows/human-in-the-loop)
 - [Agent Memory](./agent-memory)

package/dist/docs/core/01-reference.md

@@ -50,9 +50,9 @@ const memory = mastra.getMemory("conversationMemory");
 
 ## Related
 
-- [Mastra.listMemory()](https://mastra.ai/reference/v1/core/listMemory)
-- [Memory overview](https://mastra.ai/docs/v1/memory/overview)
-- [Agent Memory](https://mastra.ai/docs/v1/agents/agent-memory)
+- [Mastra.listMemory()](https://mastra.ai/reference/core/listMemory)
+- [Memory overview](https://mastra.ai/docs/memory/overview)
+- [Agent Memory](https://mastra.ai/docs/agents/agent-memory)
 
 ---
 
@@ -109,6 +109,6 @@ console.log(Object.keys(allMemory)); // ["conversationMemory", "analyticsMemory"
 
 ## Related
 
-- [Mastra.getMemory()](https://mastra.ai/reference/v1/core/getMemory)
-- [Memory overview](https://mastra.ai/docs/v1/memory/overview)
-- [Agent Memory](https://mastra.ai/docs/v1/agents/agent-memory)
+- [Mastra.getMemory()](https://mastra.ai/reference/core/getMemory)
+- [Memory overview](https://mastra.ai/docs/memory/overview)
+- [Agent Memory](https://mastra.ai/docs/agents/agent-memory)

package/dist/docs/memory/01-overview.md

@@ -2,75 +2,44 @@
 
 # Memory
 
-Memory gives your agent coherence across interactions and allows it to improve over time by retaining relevant information from past conversations.
+Memory enables your agent to remember user messages, agent replies, and tool results across interactions, giving it the context it needs to stay consistent, maintain conversation flow, and produce better answers over time.
 
-Mastra requires a [storage provider](./storage) to persist memory and supports three types:
+Mastra supports three complementary memory types:
 
-- [**Message history**](https://mastra.ai/docs/v1/memory/message-history) captures recent messages from the current conversation, providing short-term continuity and maintaining dialogue flow.
-- [**Working memory**](https://mastra.ai/docs/v1/memory/working-memory) stores persistent user-specific details such as names, preferences, goals, and other structured data.
-- [**Semantic recall**](https://mastra.ai/docs/v1/memory/semantic-recall) retrieves older messages from past conversations based on semantic relevance. Matches are retrieved using vector search and can include surrounding context for better comprehension.
+- [**Message history**](https://mastra.ai/docs/memory/message-history) - keeps recent messages from the current conversation so they can be rendered in the UI and used to maintain short-term continuity within the exchange.
+- [**Working memory**](https://mastra.ai/docs/memory/working-memory) - stores persistent, structured user data such as names, preferences, and goals.
+- [**Semantic recall**](https://mastra.ai/docs/memory/semantic-recall) - retrieves relevant messages from older conversations based on semantic meaning rather than exact keywords, mirroring how humans recall information by association. Requires a [vector database](https://mastra.ai/docs/memory/semantic-recall#storage-configuration) and an [embedding model](https://mastra.ai/docs/memory/semantic-recall#embedder-configuration).
 
-You can enable any combination of these memory types. Mastra assembles the relevant memories into the model’s context window. If the total exceeds the model's token limit, use [memory processors](https://mastra.ai/docs/v1/memory/memory-processors) to trim or filter messages before sending them to the model.
+If the combined memory exceeds the model's context limit, [memory processors](https://mastra.ai/docs/memory/memory-processors) can filter, trim, or prioritize content so the most relevant information is preserved.
 
 ## Getting started
 
-Install Mastra's memory module and the storage adapter for your preferred database (see the storage section below):
+Choose a memory option to get started:
 
-```bash 
-npm install @mastra/memory@beta @mastra/libsql@beta
-```
-
-Add the storage adapter to the main Mastra instance:
-
-```typescript title="src/mastra/index.ts"
-import { Mastra } from "@mastra/core";
-import { LibSQLStore } from "@mastra/libsql";
-
-export const mastra = new Mastra({
-  storage: new LibSQLStore({
-    id: 'mastra-storage',
-    url: ":memory:",
-  }),
-});
-```
-
-Enable memory by passing a `Memory` instance to your agent:
-
-```typescript title="src/mastra/agents/test-agent.ts"
-import { Memory } from "@mastra/memory";
-import { Agent } from "@mastra/core/agent";
-
-export const testAgent = new Agent({
-  id: "test-agent",
-  memory: new Memory({
-    options: {
-      lastMessages: 20,
-    },
-  }),
-});
-```
-When you send a new message, the model can now "see" the previous 20 messages, which gives it better context for the conversation and leads to more coherent, accurate replies.
-
-This example configures basic [message history](https://mastra.ai/docs/v1/memory/message-history). You can also enable [working memory](https://mastra.ai/docs/v1/memory/working-memory) and [semantic recall](https://mastra.ai/docs/v1/memory/semantic-recall) by passing additional options to `Memory`.
+- [Message history](https://mastra.ai/docs/memory/message-history)
+- [Working memory](https://mastra.ai/docs/memory/working-memory)
+- [Semantic recall](https://mastra.ai/docs/memory/semantic-recall)
 
 ## Storage
 
-Before enabling memory, you must first configure a storage adapter. Mastra supports multiple database providers including PostgreSQL, MongoDB, libSQL, and more.
+Before enabling memory, you must first configure a storage adapter. Mastra supports several databases including PostgreSQL, MongoDB, libSQL, and [more](https://mastra.ai/docs/memory/storage#supported-providers).
+
+Storage can be configured at the [instance level](https://mastra.ai/docs/memory/storage#instance-level-storage) (shared across all agents) or at the [agent level](https://mastra.ai/docs/memory/storage#agent-level-storage) (dedicated per agent).
 
-Storage can be configured at the instance level (shared across all agents) or at the agent level (dedicated per agent). You can also use different databases for storage and vector operations.
+For semantic recall, you can use a separate vector database like Pinecone alongside your primary storage.
 
-See the [Storage](https://mastra.ai/docs/v1/memory/storage) documentation for configuration options, supported providers, and examples.
+See the [Storage](https://mastra.ai/docs/memory/storage) documentation for configuration options, supported providers, and examples.
 
 ## Debugging memory
 
-When tracing is enabled, you can inspect exactly which messages the agent uses for context in each request. The trace output shows all memory included in the agent's context window - both recent message history and messages recalled via semantic recall.
+When [tracing](https://mastra.ai/docs/observability/tracing/overview) is enabled, you can inspect exactly which messages the agent uses for context in each request. The trace output shows all memory included in the agent's context window - both recent message history and messages recalled via semantic recall.
 
-This visibility helps you understand why an agent made specific decisions and verify that memory retrieval is working as expected.
+![Trace output showing memory context included in an agent request](https://mastra.ai/_next/image?url=%2Ftracingafter.png&w=1920&q=75)
 
-For more details on enabling and configuring tracing, see [Tracing](https://mastra.ai/docs/v1/observability/tracing/overview).
+This visibility helps you understand why an agent made specific decisions and verify that memory retrieval is working as expected.
 
-## Next Steps
+## Next steps
 
-- Learn more about [Storage](https://mastra.ai/docs/v1/memory/storage) providers and configuration options
-- Add [Message History](https://mastra.ai/docs/v1/memory/message-history), [Working Memory](https://mastra.ai/docs/v1/memory/working-memory), or [Semantic Recall](https://mastra.ai/docs/v1/memory/semantic-recall)
-- Visit [Memory configuration reference](https://mastra.ai/reference/v1/memory/memory-class) for all available options
+- Learn more about [Storage](https://mastra.ai/docs/memory/storage) providers and configuration options
+- Add [Message history](https://mastra.ai/docs/memory/message-history), [Working memory](https://mastra.ai/docs/memory/working-memory), or [Semantic recall](https://mastra.ai/docs/memory/semantic-recall)
+- Visit [Memory configuration reference](https://mastra.ai/reference/memory/memory-class) for all available options

package/dist/docs/memory/02-storage.md

@@ -2,7 +2,7 @@
 
 # Storage
 
-For Mastra to remember previous interactions, you must configure a storage adapter. Mastra is designed to work with your preferred database provider - choose from the [supported providers](#supported-providers) and pass it to your Mastra instance.
+For agents to remember previous interactions, Mastra needs a database. Use a storage adapter for one of the [supported databases](#supported-providers) and pass it to your Mastra instance. 
 
 ```typescript title="src/mastra/index.ts"
 import { Mastra } from "@mastra/core";
@@ -15,35 +15,37 @@ export const mastra = new Mastra({
   }),
 });
 ```
-On first interaction, Mastra automatically creates the necessary tables following the [core schema](https://mastra.ai/reference/v1/storage/overview#core-schema). This includes tables for messages, threads, resources, workflows, traces, and evaluation datasets.
+This configures instance-level storage, which all agents share by default. You can also configure [agent-level storage](#agent-level-storage) for isolated data boundaries.
+
+Mastra automatically creates the necessary tables on first interaction. See the [core schema](https://mastra.ai/reference/storage/overview#core-schema) for details on what gets created, including tables for messages, threads, resources, workflows, traces, and evaluation datasets.
 
 ## Supported providers
 
 Each provider page includes installation instructions, configuration parameters, and usage examples:
 
-- [libSQL Storage](https://mastra.ai/reference/v1/storage/libsql)
-- [PostgreSQL Storage](https://mastra.ai/reference/v1/storage/postgresql)
-- [MongoDB Storage](https://mastra.ai/reference/v1/storage/mongodb)
-- [Upstash Storage](https://mastra.ai/reference/v1/storage/upstash)
-- [Cloudflare D1](https://mastra.ai/reference/v1/storage/cloudflare-d1)
-- [Cloudflare Durable Objects](https://mastra.ai/reference/v1/storage/cloudflare)
-- [Convex](https://mastra.ai/reference/v1/storage/convex)
-- [DynamoDB](https://mastra.ai/reference/v1/storage/dynamodb)
-- [LanceDB](https://mastra.ai/reference/v1/storage/lance)
-- [Microsoft SQL Server](https://mastra.ai/reference/v1/storage/mssql)
+- [libSQL](https://mastra.ai/reference/storage/libsql)
+- [PostgreSQL](https://mastra.ai/reference/storage/postgresql)
+- [MongoDB](https://mastra.ai/reference/storage/mongodb)
+- [Upstash](https://mastra.ai/reference/storage/upstash)
+- [Cloudflare D1](https://mastra.ai/reference/storage/cloudflare-d1)
+- [Cloudflare Durable Objects](https://mastra.ai/reference/storage/cloudflare)
+- [Convex](https://mastra.ai/reference/storage/convex)
+- [DynamoDB](https://mastra.ai/reference/storage/dynamodb)
+- [LanceDB](https://mastra.ai/reference/storage/lance)
+- [Microsoft SQL Server](https://mastra.ai/reference/storage/mssql)
 
 > **Note:**
-libSQL is the easiest way to get started because it doesn’t require running a separate database server
+libSQL is the easiest way to get started because it doesn’t require running a separate database server.
 
 ## Configuration scope
 
-You can configure storage at two different scopes:
+Storage can be configured at the instance level (shared by all agents) or at the agent level (isolated to a specific agent).
 
 ### Instance-level storage
 
 Add storage to your Mastra instance so all agents, workflows, observability traces and scores share the same memory provider:
 
-```typescript
+```typescript title="src/mastra/index.ts"
 import { Mastra } from "@mastra/core";
 import { PostgresStore } from "@mastra/pg";
 
@@ -54,7 +56,7 @@ export const mastra = new Mastra({
   }),
 });
 
-// All agents automatically use this storage
+// Both agents inherit storage from the Mastra instance above
 const agent1 = new Agent({ id: "agent-1", memory: new Memory() });
 const agent2 = new Agent({ id: "agent-2", memory: new Memory() });
 ```
@@ -63,7 +65,7 @@ This is useful when all primitives share the same storage backend and have simil
 
 #### Composite storage
 
-Add storage to your Mastra instance using `MastraCompositeStore` and configure individual storage domains to use different storage providers.
+[Composite storage](https://mastra.ai/reference/storage/composite) is an alternative way to configure instance-level storage. Use `MastraCompositeStore` to set the `memory` domain (and any other [domains](https://mastra.ai/reference/storage/composite#storage-domains) you need) to different storage providers.
 
 ```typescript title="src/mastra/index.ts"
 import { Mastra } from "@mastra/core";
@@ -76,6 +78,7 @@ export const mastra = new Mastra({
   storage: new MastraCompositeStore({
     id: "composite",
     domains: {
+      // highlight-next-line
       memory: new MemoryLibSQL({ url: "file:./memory.db" }),
       workflows: new WorkflowsPG({ connectionString: process.env.DATABASE_URL }),
       observability: new ObservabilityStorageClickhouse({
@@ -90,14 +93,11 @@ export const mastra = new Mastra({
 
 This is useful when different types of data have different performance or operational requirements, such as low-latency storage for memory, durable storage for workflows, and high-throughput storage for observability.
 
-> **Note:**
-See [Storage Domains](https://mastra.ai/reference/v1/storage/composite#storage-domains) for more information.
-
 ### Agent-level storage
 
-Agent-level storage overrides storage configured at the instance-level. Add storage to a specific agent when you need data boundaries or compliance requirements:
+Agent-level storage overrides storage configured at the instance level. Add storage to a specific agent when you need data boundaries or compliance requirements:
 
-```typescript title="src/mastra/agents/memory-agent.ts"
+```typescript title="src/mastra/agents/your-agent.ts"
 import { Agent } from "@mastra/core/agent";
 import { Memory } from "@mastra/memory";
 import { PostgresStore } from "@mastra/pg";
@@ -113,56 +113,55 @@ export const agent = new Agent({
 });
 ```
 
-This is useful when different agents need to store data in separate databases for security, compliance, or organizational reasons.
-
-> **Mastra Cloud Store limitation**
-Agent-level storage is not supported when using [Mastra Cloud Store](https://mastra.ai/docs/v1/mastra-cloud/deployment#using-mastra-cloud-store). If you use Mastra Cloud Store, configure storage on the Mastra instance instead. This limitation does not apply if you bring your own database.
+> **Note:**
+[Mastra Cloud Store](https://mastra.ai/docs/mastra-cloud/deployment#using-mastra-cloud-store) doesn't support agent-level storage.
 
 ## Threads and resources
 
-Mastra organizes memory into threads using two identifiers:
+Mastra organizes conversations using two identifiers: 
+
+- **Thread** - a conversation session containing a sequence of messages.
+- **Resource** - the entity that owns the thread, such as a user, organization, project, or any other domain entity in your application.
 
-- **Thread**: A conversation session containing a sequence of messages (e.g., `convo_123`)
-- **Resource**: An identifier for the entity the thread belongs to, typically a user (e.g., `user_123`)
+Both identifiers are required for agents to store information:
 
-Both identifiers are required for agents to store and recall information:
+  **generate:**
 
 ```typescript
-const stream = await agent.stream("message for agent", {
+const response = await agent.generate("hello", {
   memory: {
-    thread: "convo_123",
+    thread: "conversation-abc-123",
     resource: "user_123",
   },
 });
 ```
 
-> **Note:**
-[Studio](https://mastra.ai/docs/v1/getting-started/studio) automatically generates a thread and resource ID for you. Remember to  to pass these explicitly when calling `stream` or `generate` yourself.
-
-### Thread and resource relationship
+  
+  **stream:**
 
-Each thread has an owner (its `resourceId`) that is set when the thread is created and cannot be changed. When you query a thread, you must use the correct owner's resource ID. Attempting to query a thread with a different resource ID will result in an error:
-
-```text
-Thread with id <thread_id> is for resource with id <resource_a>
-but resource <resource_b> was queried
+```typescript
+const stream = await agent.stream("hello", {
+  memory: {
+    thread: "conversation-abc-123",
+    resource: "user_123",
+  },
+});
 ```
 
-Note that while each thread has one owner, messages within that thread can have different `resourceId` values. This is used for message attribution and filtering (e.g., distinguishing between different agents in a multi-agent system, or filtering messages for analytics).
-
-**Security:** Memory is a storage layer, not an authorization layer. Your application must implement access control before calling memory APIs. The `resourceId` parameter controls both validation and filtering - provide it to validate ownership and filter messages, or omit it for server-side access without validation.
+  
 
-To avoid accidentally reusing thread IDs across different owners, use UUIDs: `crypto.randomUUID()`
+> **Note:**
+[Studio](https://mastra.ai/docs/getting-started/studio) automatically generates a thread and resource ID for you. When calling `stream()` or `generate()` yourself, remember to provide these identifiers explicitly.
 
 ### Thread title generation
 
-Mastra can automatically generate descriptive thread titles based on the user's first message.
+Mastra can automatically generate descriptive thread titles based on the user's first message when `generateTitle` is enabled.
 
 Use this option when implementing a ChatGPT-style chat interface to render a title alongside each thread in the conversation list (for example, in a sidebar) derived from the thread’s initial user message.
 
-```typescript
-export const testAgent = new Agent({
-  id: "test-agent",
+```typescript title="src/mastra/agents/my-agent.ts"
+export const agent = new Agent({
+  id: "agent",
   memory: new Memory({
     options: {
       generateTitle: true,
@@ -173,16 +172,16 @@ export const testAgent = new Agent({
 
 Title generation runs asynchronously after the agent responds and does not affect response time.
 
-To optimize cost or behavior, provide a smaller `model` and custom `instructions`:
+To optimize cost or behavior, provide a smaller [`model`](/models) and custom `instructions`:
 
-```typescript
-export const testAgent = new Agent({
-  id: "test-agent",
+```typescript title="src/mastra/agents/my-agent.ts"
+export const agent = new Agent({
+  id: "agent",
   memory: new Memory({
     options: {
       generateTitle: {
         model: "openai/gpt-4o-mini",
-        instructions: "Generate a concise title based on the user's first message",
+        instructions: "Generate a 1 word title",
       },
     },
   }),
@@ -191,43 +190,72 @@ export const testAgent = new Agent({
 
 ## Semantic recall
 
-Semantic recall uses vector embeddings to retrieve relevant past messages based on meaning rather than recency. This requires a vector database instance, which can be configured at the instance or agent level.
+Semantic recall has different storage requirements - it needs a vector database in addition to the standard storage adapter. See [Semantic recall](https://mastra.ai/docs/memory/semantic-recall) for setup and supported vector providers.
 
-The vector database doesn't have to be the same as your storage provider. For example, you might use PostgreSQL for storage and Pinecone for vectors:
+## Handling large attachments
 
-```typescript
-import { Mastra } from "@mastra/core";
-import { Agent } from "@mastra/core/agent";
-import { Memory } from "@mastra/memory";
-import { PostgresStore } from "@mastra/pg";
-import { PineconeVector } from "@mastra/pinecone";
+Some storage providers enforce record size limits that base64-encoded file attachments (such as images) can exceed:
 
-// Instance-level vector configuration
-export const mastra = new Mastra({
-  storage: new PostgresStore({
-    id: 'mastra-storage',
-    connectionString: process.env.DATABASE_URL,
-  }),
-});
+| Provider | Record size limit |
+| -------- | ----------------- |
+| [DynamoDB](https://mastra.ai/reference/storage/dynamodb) | 400 KB |
+| [Convex](https://mastra.ai/reference/storage/convex) | 1 MiB |
+| [Cloudflare D1](https://mastra.ai/reference/storage/cloudflare-d1) | 1 MiB |
 
-// Agent-level vector configuration
-export const agent = new Agent({
-  id: "agent",
-  memory: new Memory({
-    vector: new PineconeVector({
-      id: 'agent-vector',
-      apiKey: process.env.PINECONE_API_KEY,
-    }),
-    options: {
-      semanticRecall: {
-        topK: 5,
-        messageRange: 2,
-      },
-    },
-  }),
-});
+PostgreSQL, MongoDB, and libSQL have higher limits and are generally unaffected.
+
+To avoid this, use an input processor to upload attachments to external storage (S3, R2, GCS, [Convex file storage](https://docs.convex.dev/file-storage), etc.) and replace them with URL references before persistence.
+
+```typescript title="src/mastra/processors/attachment-uploader.ts"
+import type { Processor } from "@mastra/core/processors";
+import type { MastraDBMessage } from "@mastra/core/memory";
+
+export class AttachmentUploader implements Processor {
+  id = "attachment-uploader";
+
+  async processInput({ messages }: { messages: MastraDBMessage[] }) {
+    return Promise.all(messages.map((msg) => this.processMessage(msg)));
+  }
+
+  async processMessage(msg: MastraDBMessage) {
+    const attachments = msg.content.experimental_attachments;
+    if (!attachments?.length) return msg;
+
+    const uploaded = await Promise.all(
+      attachments.map(async (att) => {
+        // Skip if already a URL
+        if (!att.url?.startsWith("data:")) return att;
+
+        // Upload base64 data and replace with URL
+        const url = await this.upload(att.url, att.contentType);
+        return { ...att, url };
+      })
+    );
+
+    return { ...msg, content: { ...msg.content, experimental_attachments: uploaded } };
+  }
+
+  async upload(dataUri: string, contentType?: string): Promise<string> {
+    const base64 = dataUri.split(",")[1];
+    const buffer = Buffer.from(base64, "base64");
+
+    // Replace with your storage provider (S3, R2, GCS, Convex, etc.)
+    // return await s3.upload(buffer, contentType);
+    throw new Error("Implement upload() with your storage provider");
+  }
+}
 ```
 
-We support all popular vector providers including [Pinecone](https://mastra.ai/reference/v1/vectors/pinecone), [Chroma](https://mastra.ai/reference/v1/vectors/chroma), [Qdrant](https://mastra.ai/reference/v1/vectors/qdrant), and many more.
+Use the processor with your agent:
 
-For more information on configuring semantic recall, see the [Semantic Recall](./semantic-recall) documentation.
+```typescript
+import { Agent } from "@mastra/core/agent";
+import { Memory } from "@mastra/memory";
+import { AttachmentUploader } from "./processors/attachment-uploader";
+
+const agent = new Agent({
+  id: "my-agent",
+  memory: new Memory({ storage: yourStorage }),
+  inputProcessors: [new AttachmentUploader()],
+});
+```