@mastra/memory 0.2.7-alpha.2 → 0.2.7-alpha.3

package/.turbo/turbo-build.log

@@ -1,29 +1,29 @@
 
-> @mastra/memory@0.2.7-alpha.2 build /home/runner/work/mastra/mastra/packages/memory
+> @mastra/memory@0.2.7-alpha.3 build /home/runner/work/mastra/mastra/packages/memory
 > pnpm run check && tsup src/index.ts src/processors/index.ts --format esm,cjs --experimental-dts --clean --treeshake=smallest --splitting
 
 
-> @mastra/memory@0.2.7-alpha.2 check /home/runner/work/mastra/mastra/packages/memory
+> @mastra/memory@0.2.7-alpha.3 check /home/runner/work/mastra/mastra/packages/memory
 > tsc --noEmit
 
 CLI Building entry: src/index.ts, src/processors/index.ts
 CLI Using tsconfig: tsconfig.json
 CLI tsup v8.4.0
 TSC Build start
-TSC ⚡️ Build success in 11238ms
+TSC ⚡️ Build success in 11095ms
 DTS Build start
 CLI Target: es2022
 Analysis will use the bundled TypeScript version 5.8.2
 Writing package typings: /home/runner/work/mastra/mastra/packages/memory/dist/_tsup-dts-rollup.d.ts
 Analysis will use the bundled TypeScript version 5.8.2
 Writing package typings: /home/runner/work/mastra/mastra/packages/memory/dist/_tsup-dts-rollup.d.cts
-DTS ⚡️ Build success in 5847ms
+DTS ⚡️ Build success in 6446ms
 CLI Cleaning output folder
 ESM Build start
 CJS Build start
-ESM dist/index.js            13.60 KB
-ESM dist/processors/index.js 5.33 KB
-ESM ⚡️ Build success in 238ms
-CJS dist/index.cjs            13.62 KB
+CJS dist/index.cjs            13.53 KB
 CJS dist/processors/index.cjs 5.54 KB
-CJS ⚡️ Build success in 238ms
+CJS ⚡️ Build success in 411ms
+ESM dist/processors/index.js 5.33 KB
+ESM dist/index.js            13.50 KB
+ESM ⚡️ Build success in 412ms

package/CHANGELOG.md

@@ -1,5 +1,23 @@
 # @mastra/memory
 
+## 0.2.7-alpha.3
+
+### Patch Changes
+
+- 5ae0180: Removed prefixed doc references
+- 3e72f94: Updated the internal working memory system to use MD for formatting instead of nested XML - this is more token efficient and makes it more obvious that it's unstructured text
+- Updated dependencies [5ae0180]
+- Updated dependencies [9bfa12b]
+- Updated dependencies [515ebfb]
+- Updated dependencies [88fa727]
+- Updated dependencies [f37f535]
+- Updated dependencies [4d67826]
+- Updated dependencies [6330967]
+- Updated dependencies [8393832]
+- Updated dependencies [6330967]
+  - @mastra/core@0.8.0-alpha.3
+  - @mastra/rag@0.1.15-alpha.3
+
 ## 0.2.7-alpha.2
 
 ### Patch Changes

package/README.md

@@ -1,6 +1,6 @@
 # Mastra Memory
 
-Memory management for Mastra agents. Visit [the docs](https://mastra.ai/docs/agents/01-agent-memory) for more information.
+Memory management for Mastra agents. Visit [the docs](https://mastra.ai/docs/agents/agent-memory) for more information.
 
 ## License
 

package/dist/index.cjs

@@ -10,7 +10,7 @@ var zod = require('zod');
 var updateWorkingMemoryTool = {
   description: "Update the working memory with new information",
   parameters: zod.z.object({
-    memory: zod.z.string().describe("The XML-formatted working memory content to store")
+    memory: zod.z.string().describe("The Markdown-formatted working memory content to store")
   }),
   execute: async (params) => {
     const { context, threadId, memory } = params;
@@ -254,8 +254,7 @@ var Memory = class extends memory.MastraMemory {
     const thread = await this.storage.__getThreadById({ threadId });
     if (!thread) return this.threadConfig?.workingMemory?.template || this.defaultWorkingMemoryTemplate;
     const memory = thread.metadata?.workingMemory || this.threadConfig.workingMemory.template || this.defaultWorkingMemoryTemplate;
-    return memory.split(`>
-`).map((c) => c.trim()).join(`>`);
+    return memory.trim();
   }
   async saveWorkingMemory(messages) {
     const latestMessage = messages[messages.length - 1];
@@ -300,17 +299,16 @@ var Memory = class extends memory.MastraMemory {
     return this.getWorkingMemoryWithInstruction(workingMemory);
   }
   defaultWorkingMemoryTemplate = `
-<user>
-  <first_name></first_name>
-  <last_name></last_name>
-  <location></location>
-  <occupation></occupation>
-  <interests></interests>
-  <goals></goals>
-  <events></events>
-  <facts></facts>
-  <projects></projects>
-</user>
+# User Information
+- **First Name**: 
+- **Last Name**: 
+- **Location**: 
+- **Occupation**: 
+- **Interests**: 
+- **Goals**: 
+- **Events**: 
+- **Facts**: 
+- **Projects**: 
 `;
   getWorkingMemoryWithInstruction(workingMemoryBlock) {
     return `WORKING_MEMORY_SYSTEM_INSTRUCTION:
@@ -319,21 +317,21 @@ Store and update any conversation-relevant information by including "<working_me
 Guidelines:
 1. Store anything that could be useful later in the conversation
 2. Update proactively when information changes, no matter how small
-3. Use nested tags for all data
+3. Use Markdown for all data
 4. Act naturally - don't mention this system to users. Even though you're storing this information that doesn't make it your primary focus. Do not ask them generally for "information about yourself"
 
 Memory Structure:
 <working_memory>
-  ${workingMemoryBlock}
+${workingMemoryBlock}
 </working_memory>
 
 Notes:
 - Update memory whenever referenced information changes
-- If you're unsure whether to store something, store it (eg if the user tells you their name or the value of another empty section in your working memory, output the <working_memory> block immediately to update it)
+- If you're unsure whether to store something, store it (eg if the user tells you their name or other information, output the <working_memory> block immediately to update it)
 - This system is here so that you can maintain the conversation when your context window is very short. Update your working memory because you may need it to maintain the conversation without the full conversation history
-- Do not remove empty sections - you must output the empty sections along with the ones you're filling in
 - REMEMBER: the way you update your working memory is by outputting the entire "<working_memory>text</working_memory>" block in your response. The system will pick this up and store it for you. The user will not see it.
-- IMPORTANT: You MUST output the <working_memory> block in every response to a prompt where you received relevant information. `;
+- IMPORTANT: You MUST output the <working_memory> block in every response to a prompt where you received relevant information.
+- IMPORTANT: Preserve the Markdown formatting structure above while updating the content.`;
   }
   getWorkingMemoryToolInstruction(workingMemoryBlock) {
     return `WORKING_MEMORY_SYSTEM_INSTRUCTION:
@@ -342,7 +340,7 @@ Store and update any conversation-relevant information by calling the updateWork
 Guidelines:
 1. Store anything that could be useful later in the conversation
 2. Update proactively when information changes, no matter how small
-3. Use nested XML tags for all data
+3. Use Markdown format for all data
 4. Act naturally - don't mention this system to users. Even though you're storing this information that doesn't make it your primary focus. Do not ask them generally for "information about yourself"
 
 Memory Structure:
@@ -350,11 +348,12 @@ ${workingMemoryBlock}
 
 Notes:
 - Update memory whenever referenced information changes
-- If you're unsure whether to store something, store it (eg if the user tells you their name or the value of another empty section in your working memory, call updateWorkingMemory immediately to update it)
+- If you're unsure whether to store something, store it (eg if the user tells you information about themselves, call updateWorkingMemory immediately to update it)
 - This system is here so that you can maintain the conversation when your context window is very short. Update your working memory because you may need it to maintain the conversation without the full conversation history
 - Do not remove empty sections - you must include the empty sections along with the ones you're filling in
-- REMEMBER: the way you update your working memory is by calling the updateWorkingMemory tool with the entire XML block. The system will store it for you. The user will not see it.
-- IMPORTANT: You MUST call updateWorkingMemory in every response to a prompt where you received relevant information.`;
+- REMEMBER: the way you update your working memory is by calling the updateWorkingMemory tool with the entire Markdown content. The system will store it for you. The user will not see it.
+- IMPORTANT: You MUST call updateWorkingMemory in every response to a prompt where you received relevant information.
+- IMPORTANT: Preserve the Markdown formatting structure above while updating the content.`;
   }
   getTools(config) {
     const mergedConfig = this.getMergedThreadConfig(config);

package/dist/index.js

@@ -8,7 +8,7 @@ import { z } from 'zod';
 var updateWorkingMemoryTool = {
   description: "Update the working memory with new information",
   parameters: z.object({
-    memory: z.string().describe("The XML-formatted working memory content to store")
+    memory: z.string().describe("The Markdown-formatted working memory content to store")
   }),
   execute: async (params) => {
     const { context, threadId, memory } = params;
@@ -252,8 +252,7 @@ var Memory = class extends MastraMemory {
     const thread = await this.storage.__getThreadById({ threadId });
     if (!thread) return this.threadConfig?.workingMemory?.template || this.defaultWorkingMemoryTemplate;
     const memory = thread.metadata?.workingMemory || this.threadConfig.workingMemory.template || this.defaultWorkingMemoryTemplate;
-    return memory.split(`>
-`).map((c) => c.trim()).join(`>`);
+    return memory.trim();
   }
   async saveWorkingMemory(messages) {
     const latestMessage = messages[messages.length - 1];
@@ -298,17 +297,16 @@ var Memory = class extends MastraMemory {
     return this.getWorkingMemoryWithInstruction(workingMemory);
   }
   defaultWorkingMemoryTemplate = `
-<user>
-  <first_name></first_name>
-  <last_name></last_name>
-  <location></location>
-  <occupation></occupation>
-  <interests></interests>
-  <goals></goals>
-  <events></events>
-  <facts></facts>
-  <projects></projects>
-</user>
+# User Information
+- **First Name**: 
+- **Last Name**: 
+- **Location**: 
+- **Occupation**: 
+- **Interests**: 
+- **Goals**: 
+- **Events**: 
+- **Facts**: 
+- **Projects**: 
 `;
   getWorkingMemoryWithInstruction(workingMemoryBlock) {
     return `WORKING_MEMORY_SYSTEM_INSTRUCTION:
@@ -317,21 +315,21 @@ Store and update any conversation-relevant information by including "<working_me
 Guidelines:
 1. Store anything that could be useful later in the conversation
 2. Update proactively when information changes, no matter how small
-3. Use nested tags for all data
+3. Use Markdown for all data
 4. Act naturally - don't mention this system to users. Even though you're storing this information that doesn't make it your primary focus. Do not ask them generally for "information about yourself"
 
 Memory Structure:
 <working_memory>
-  ${workingMemoryBlock}
+${workingMemoryBlock}
 </working_memory>
 
 Notes:
 - Update memory whenever referenced information changes
-- If you're unsure whether to store something, store it (eg if the user tells you their name or the value of another empty section in your working memory, output the <working_memory> block immediately to update it)
+- If you're unsure whether to store something, store it (eg if the user tells you their name or other information, output the <working_memory> block immediately to update it)
 - This system is here so that you can maintain the conversation when your context window is very short. Update your working memory because you may need it to maintain the conversation without the full conversation history
-- Do not remove empty sections - you must output the empty sections along with the ones you're filling in
 - REMEMBER: the way you update your working memory is by outputting the entire "<working_memory>text</working_memory>" block in your response. The system will pick this up and store it for you. The user will not see it.
-- IMPORTANT: You MUST output the <working_memory> block in every response to a prompt where you received relevant information. `;
+- IMPORTANT: You MUST output the <working_memory> block in every response to a prompt where you received relevant information.
+- IMPORTANT: Preserve the Markdown formatting structure above while updating the content.`;
   }
   getWorkingMemoryToolInstruction(workingMemoryBlock) {
     return `WORKING_MEMORY_SYSTEM_INSTRUCTION:
@@ -340,7 +338,7 @@ Store and update any conversation-relevant information by calling the updateWork
 Guidelines:
 1. Store anything that could be useful later in the conversation
 2. Update proactively when information changes, no matter how small
-3. Use nested XML tags for all data
+3. Use Markdown format for all data
 4. Act naturally - don't mention this system to users. Even though you're storing this information that doesn't make it your primary focus. Do not ask them generally for "information about yourself"
 
 Memory Structure:
@@ -348,11 +346,12 @@ ${workingMemoryBlock}
 
 Notes:
 - Update memory whenever referenced information changes
-- If you're unsure whether to store something, store it (eg if the user tells you their name or the value of another empty section in your working memory, call updateWorkingMemory immediately to update it)
+- If you're unsure whether to store something, store it (eg if the user tells you information about themselves, call updateWorkingMemory immediately to update it)
 - This system is here so that you can maintain the conversation when your context window is very short. Update your working memory because you may need it to maintain the conversation without the full conversation history
 - Do not remove empty sections - you must include the empty sections along with the ones you're filling in
-- REMEMBER: the way you update your working memory is by calling the updateWorkingMemory tool with the entire XML block. The system will store it for you. The user will not see it.
-- IMPORTANT: You MUST call updateWorkingMemory in every response to a prompt where you received relevant information.`;
+- REMEMBER: the way you update your working memory is by calling the updateWorkingMemory tool with the entire Markdown content. The system will store it for you. The user will not see it.
+- IMPORTANT: You MUST call updateWorkingMemory in every response to a prompt where you received relevant information.
+- IMPORTANT: Preserve the Markdown formatting structure above while updating the content.`;
   }
   getTools(config) {
     const mergedConfig = this.getMergedThreadConfig(config);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/memory",
-  "version": "0.2.7-alpha.2",
+  "version": "0.2.7-alpha.3",
   "description": "",
   "type": "module",
   "main": "./dist/index.js",
@@ -40,8 +40,8 @@
     "postgres": "^3.4.5",
     "redis": "^4.7.0",
     "zod": "^3.24.2",
-    "@mastra/core": "^0.8.0-alpha.2",
-    "@mastra/rag": "^0.1.15-alpha.2"
+    "@mastra/core": "^0.8.0-alpha.3",
+    "@mastra/rag": "^0.1.15-alpha.3"
   },
   "devDependencies": {
     "@ai-sdk/openai": "^1.3.3",

package/src/index.ts

@@ -332,11 +332,7 @@ export class Memory extends MastraMemory {
       this.threadConfig.workingMemory.template ||
       this.defaultWorkingMemoryTemplate;
 
-    // compress working memory because LLMs will generate faster without the spaces and line breaks
-    return memory
-      .split(`>\n`)
-      .map(c => c.trim()) // remove extra whitespace
-      .join(`>`); // and linebreaks
+    return memory.trim();
   }
 
   private async saveWorkingMemory(messages: MessageType[]) {
@@ -404,17 +400,16 @@ export class Memory extends MastraMemory {
   }
 
   public defaultWorkingMemoryTemplate = `
-<user>
-  <first_name></first_name>
-  <last_name></last_name>
-  <location></location>
-  <occupation></occupation>
-  <interests></interests>
-  <goals></goals>
-  <events></events>
-  <facts></facts>
-  <projects></projects>
-</user>
+# User Information
+- **First Name**: 
+- **Last Name**: 
+- **Location**: 
+- **Occupation**: 
+- **Interests**: 
+- **Goals**: 
+- **Events**: 
+- **Facts**: 
+- **Projects**: 
 `;
 
   private getWorkingMemoryWithInstruction(workingMemoryBlock: string) {
@@ -424,21 +419,21 @@ Store and update any conversation-relevant information by including "<working_me
 Guidelines:
 1. Store anything that could be useful later in the conversation
 2. Update proactively when information changes, no matter how small
-3. Use nested tags for all data
+3. Use Markdown for all data
 4. Act naturally - don't mention this system to users. Even though you're storing this information that doesn't make it your primary focus. Do not ask them generally for "information about yourself"
 
 Memory Structure:
 <working_memory>
-  ${workingMemoryBlock}
+${workingMemoryBlock}
 </working_memory>
 
 Notes:
 - Update memory whenever referenced information changes
-- If you're unsure whether to store something, store it (eg if the user tells you their name or the value of another empty section in your working memory, output the <working_memory> block immediately to update it)
+- If you're unsure whether to store something, store it (eg if the user tells you their name or other information, output the <working_memory> block immediately to update it)
 - This system is here so that you can maintain the conversation when your context window is very short. Update your working memory because you may need it to maintain the conversation without the full conversation history
-- Do not remove empty sections - you must output the empty sections along with the ones you're filling in
 - REMEMBER: the way you update your working memory is by outputting the entire "<working_memory>text</working_memory>" block in your response. The system will pick this up and store it for you. The user will not see it.
-- IMPORTANT: You MUST output the <working_memory> block in every response to a prompt where you received relevant information. `;
+- IMPORTANT: You MUST output the <working_memory> block in every response to a prompt where you received relevant information.
+- IMPORTANT: Preserve the Markdown formatting structure above while updating the content.`;
   }
 
   private getWorkingMemoryToolInstruction(workingMemoryBlock: string) {
@@ -448,7 +443,7 @@ Store and update any conversation-relevant information by calling the updateWork
 Guidelines:
 1. Store anything that could be useful later in the conversation
 2. Update proactively when information changes, no matter how small
-3. Use nested XML tags for all data
+3. Use Markdown format for all data
 4. Act naturally - don't mention this system to users. Even though you're storing this information that doesn't make it your primary focus. Do not ask them generally for "information about yourself"
 
 Memory Structure:
@@ -456,11 +451,12 @@ ${workingMemoryBlock}
 
 Notes:
 - Update memory whenever referenced information changes
-- If you're unsure whether to store something, store it (eg if the user tells you their name or the value of another empty section in your working memory, call updateWorkingMemory immediately to update it)
+- If you're unsure whether to store something, store it (eg if the user tells you information about themselves, call updateWorkingMemory immediately to update it)
 - This system is here so that you can maintain the conversation when your context window is very short. Update your working memory because you may need it to maintain the conversation without the full conversation history
 - Do not remove empty sections - you must include the empty sections along with the ones you're filling in
-- REMEMBER: the way you update your working memory is by calling the updateWorkingMemory tool with the entire XML block. The system will store it for you. The user will not see it.
-- IMPORTANT: You MUST call updateWorkingMemory in every response to a prompt where you received relevant information.`;
+- REMEMBER: the way you update your working memory is by calling the updateWorkingMemory tool with the entire Markdown content. The system will store it for you. The user will not see it.
+- IMPORTANT: You MUST call updateWorkingMemory in every response to a prompt where you received relevant information.
+- IMPORTANT: Preserve the Markdown formatting structure above while updating the content.`;
   }
 
   public getTools(config?: MemoryConfig): Record<string, CoreTool> {

package/src/processors/index.test.ts

@@ -3,11 +3,13 @@ import { createTool } from '@mastra/core';
 import type { CoreMessage, MessageType } from '@mastra/core';
 import { Agent } from '@mastra/core/agent';
 import cl100k_base from 'js-tiktoken/ranks/cl100k_base';
-import { describe, it, expect } from 'vitest';
+import { describe, it, expect, vi } from 'vitest';
 import { z } from 'zod';
 import { generateConversationHistory } from '../../integration-tests/src/test-utils';
 import { TokenLimiter, ToolCallFilter } from './index';
 
+vi.setConfig({ testTimeout: 20_000, hookTimeout: 20_000 });
+
 describe('TokenLimiter', () => {
   it('should limit messages to the specified token count', () => {
     // Create messages with predictable token counts (approximately 25 tokens each)

package/src/tools/working-memory.ts

@@ -4,7 +4,7 @@ import { z } from 'zod';
 export const updateWorkingMemoryTool: CoreTool = {
   description: 'Update the working memory with new information',
   parameters: z.object({
-    memory: z.string().describe('The XML-formatted working memory content to store'),
+    memory: z.string().describe('The Markdown-formatted working memory content to store'),
   }),
   execute: async (params: any) => {
     const { context, threadId, memory } = params;