@elizaos/plugin-memory 1.1.1 → 2.0.0-alpha

package/dist/evaluators/index.d.ts

@@ -0,0 +1,3 @@
+export { longTermExtractionEvaluator } from "./long-term-extraction";
+export { summarizationEvaluator } from "./summarization";
+//# sourceMappingURL=index.d.ts.map

package/dist/evaluators/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/evaluators/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,2BAA2B,EAAE,MAAM,wBAAwB,CAAC;AACrE,OAAO,EAAE,sBAAsB,EAAE,MAAM,iBAAiB,CAAC"}

package/dist/evaluators/long-term-extraction.d.ts

@@ -1,8 +1,3 @@
 import { type Evaluator } from "@elizaos/core";
-/**
- * Long-term Memory Extraction Evaluator
- *
- * Analyzes conversations to extract persistent facts about users that should be remembered
- * across all future conversations.
- */
 export declare const longTermExtractionEvaluator: Evaluator;
+//# sourceMappingURL=long-term-extraction.d.ts.map

package/dist/evaluators/long-term-extraction.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"long-term-extraction.d.ts","sourceRoot":"","sources":["../../src/evaluators/long-term-extraction.ts"],"names":[],"mappings":"AAAA,OAAO,EAEL,KAAK,SAAS,EAKf,MAAM,eAAe,CAAC;AAgCvB,eAAO,MAAM,2BAA2B,EAAE,SAsHzC,CAAC"}

package/dist/evaluators/summarization.d.ts

@@ -1,30 +1,3 @@
 import { type Evaluator } from "@elizaos/core";
-/**
- * Short-term Memory Summarization Evaluator
- *
- * Automatically generates and updates conversation summaries when conversations
- * exceed the configured threshold (default: 16 messages).
- *
- * BEHAVIOR:
- * - Monitors message count per room
- * - Creates initial summary when count >= threshold (e.g., 16 messages)
- * - Updates summary at regular intervals (e.g., every 10 new messages)
- * - Condenses existing summary with new messages to stay under token limit
- * - Tracks offset to avoid re-processing messages
- * - Caps new messages per update to prevent context bloat (default: 20)
- *
- * OPTIMIZATION:
- * - Only triggers LLM when crossing threshold or interval boundaries
- * - Processes only NEW messages since last update
- * - Maintains rolling summary (fixed size, not ever-growing)
- * - LLM is instructed to merge and condense, keeping under 2500 tokens
- *
- * INTEGRATION:
- * Works with shortTermMemoryProvider which:
- * - Shows full conversation when < threshold (no summarization needed)
- * - Shows summaries + recent messages when >= threshold (optimized context)
- *
- * This creates an adaptive system that starts with full context and seamlessly
- * transitions to efficient summarization as conversations grow.
- */
 export declare const summarizationEvaluator: Evaluator;
+//# sourceMappingURL=summarization.d.ts.map

package/dist/evaluators/summarization.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"summarization.d.ts","sourceRoot":"","sources":["../../src/evaluators/summarization.ts"],"names":[],"mappings":"AAAA,OAAO,EAEL,KAAK,SAAS,EAMf,MAAM,eAAe,CAAC;AA+CvB,eAAO,MAAM,sBAAsB,EAAE,SAgMpC,CAAC"}

package/dist/generated/prompts/typescript/prompts.d.ts

@@ -0,0 +1,16 @@
+/**
+ * Auto-generated prompt templates
+ * DO NOT EDIT - Generated from ../../../../../prompts/*.txt
+ *
+ * These prompts use Handlebars-style template syntax:
+ * - {{variableName}} for simple substitution
+ * - {{#each items}}...{{/each}} for iteration
+ * - {{#if condition}}...{{/if}} for conditionals
+ */
+export declare const initialSummarizationTemplate = "# Task: Summarize Conversation\n\nYou are analyzing a conversation to create a concise summary that captures the key points, topics, and important details.\n\n# Recent Messages\n{{recentMessages}}\n\n# Instructions\nGenerate a summary that:\n1. Captures the main topics discussed\n2. Highlights key information shared\n3. Notes any decisions made or questions asked\n4. Maintains context for future reference\n5. Is concise but comprehensive\n\n**IMPORTANT**: Keep the summary under 2500 tokens. Be comprehensive but concise.\n\nAlso extract:\n- **Topics**: List of main topics discussed (comma-separated)\n- **Key Points**: Important facts or decisions (bullet points)\n\nRespond in this XML format:\n<summary>\n  <text>Your comprehensive summary here</text>\n  <topics>topic1, topic2, topic3</topics>\n  <keyPoints>\n    <point>First key point</point>\n    <point>Second key point</point>\n  </keyPoints>\n</summary>";
+export declare const INITIAL_SUMMARIZATION_TEMPLATE = "# Task: Summarize Conversation\n\nYou are analyzing a conversation to create a concise summary that captures the key points, topics, and important details.\n\n# Recent Messages\n{{recentMessages}}\n\n# Instructions\nGenerate a summary that:\n1. Captures the main topics discussed\n2. Highlights key information shared\n3. Notes any decisions made or questions asked\n4. Maintains context for future reference\n5. Is concise but comprehensive\n\n**IMPORTANT**: Keep the summary under 2500 tokens. Be comprehensive but concise.\n\nAlso extract:\n- **Topics**: List of main topics discussed (comma-separated)\n- **Key Points**: Important facts or decisions (bullet points)\n\nRespond in this XML format:\n<summary>\n  <text>Your comprehensive summary here</text>\n  <topics>topic1, topic2, topic3</topics>\n  <keyPoints>\n    <point>First key point</point>\n    <point>Second key point</point>\n  </keyPoints>\n</summary>";
+export declare const longTermExtractionTemplate = "# Task: Extract Long-Term Memory (Strict Criteria)\n\nYou are analyzing a conversation to extract ONLY the most critical, persistent information about the user using cognitive science memory categories.\n\n# Recent Messages\n{{recentMessages}}\n\n# Current Long-Term Memories\n{{existingMemories}}\n\n# Memory Categories (Based on Cognitive Science)\n\n## 1. EPISODIC Memory\nPersonal experiences and specific events with temporal/spatial context.\n**Examples:**\n- \"User completed migration project from MongoDB to PostgreSQL in Q2 2024\"\n- \"User encountered authentication bug in production on March 15th\"\n- \"User had a negative experience with Docker networking in previous job\"\n\n**Requirements:**\n- Must include WHO did WHAT, WHEN/WHERE\n- Must be a specific, concrete event (not a pattern)\n- Must have significant impact or relevance to future work\n\n## 2. SEMANTIC Memory\nGeneral facts, concepts, knowledge, and established truths about the user.\n**Examples:**\n- \"User is a senior backend engineer with 8 years experience\"\n- \"User specializes in distributed systems and microservices architecture\"\n- \"User's primary programming language is TypeScript\"\n- \"User works at Acme Corp as technical lead\"\n\n**Requirements:**\n- Must be factual, timeless information\n- Must be explicitly stated or demonstrated conclusively\n- No speculation or inference from single instances\n- Core identity, expertise, or knowledge only\n\n## 3. PROCEDURAL Memory\nSkills, workflows, methodologies, and how-to knowledge.\n**Examples:**\n- \"User follows strict TDD workflow: write tests first, then implementation\"\n- \"User prefers git rebase over merge to maintain linear history\"\n- \"User's debugging process: check logs \u2192 reproduce locally \u2192 binary search\"\n- \"User always writes JSDoc comments before implementing functions\"\n\n**Requirements:**\n- Must describe HOW user does something\n- Must be a repeated, consistent pattern (seen 3+ times or explicitly stated as standard practice)\n- Must be a workflow, methodology, or skill application\n- Not one-off preferences\n\n# ULTRA-STRICT EXTRACTION CRITERIA\n\n## \u2705 DO EXTRACT (Only These):\n\n**EPISODIC:**\n- Significant completed projects or milestones\n- Important bugs, incidents, or problems encountered\n- Major decisions made with lasting impact\n- Formative experiences that shape future work\n\n**SEMANTIC:**\n- Professional identity (role, title, company)\n- Core expertise and specializations (stated explicitly or demonstrated conclusively)\n- Primary languages, frameworks, or tools (not exploratory use)\n- Established facts about their work context\n\n**PROCEDURAL:**\n- Consistent workflows demonstrated 3+ times or explicitly stated\n- Standard practices user always follows\n- Methodology preferences with clear rationale\n- Debugging, testing, or development processes\n\n## \u274C NEVER EXTRACT:\n\n- **One-time requests or tasks** (e.g., \"can you generate an image\", \"help me debug this\")\n- **Casual conversations** without lasting significance\n- **Exploratory questions** (e.g., \"how does X work?\")\n- **Temporary context** (current bug, today's task)\n- **Preferences from single occurrence** (e.g., user asked for code once)\n- **Social pleasantries** (thank you, greetings)\n- **Testing or experimentation** (trying out a feature)\n- **Common patterns everyone has** (likes clear explanations)\n- **Situational information** (working on feature X today)\n- **Opinions without persistence** (single complaint, isolated praise)\n- **General knowledge** (not specific to user)\n\n# Quality Gates (ALL Must Pass)\n\n1. **Significance Test**: Will this matter in 3+ months?\n2. **Specificity Test**: Is this concrete and actionable?\n3. **Evidence Test**: Is there strong evidence (3+ instances OR explicit self-identification)?\n4. **Uniqueness Test**: Is this specific to THIS user (not generic)?\n5. **Confidence Test**: Confidence must be >= 0.85 (be VERY conservative)\n6. **Non-Redundancy Test**: Does this add NEW information not in existing memories?\n\n# Confidence Scoring (Be Conservative)\n\n- **0.95-1.0**: User explicitly stated as core identity/practice AND demonstrated multiple times\n- **0.85-0.94**: User explicitly stated OR consistently demonstrated 5+ times\n- **0.75-0.84**: Strong pattern (3-4 instances) with supporting context\n- **Below 0.75**: DO NOT EXTRACT (insufficient evidence)\n\n# Critical Instructions\n\n1. **Default to NOT extracting** - When in doubt, skip it\n2. **Require overwhelming evidence** - One or two mentions is NOT enough\n3. **Focus on what's PERSISTENT** - Not what's temporary or situational\n4. **Verify against existing memories** - Don't duplicate or contradict\n5. **Maximum 2-3 extractions per run** - Quality over quantity\n\n**If there are no qualifying facts (which is common), respond with <memories></memories>**\n\n# Response Format\n\n<memories>\n  <memory>\n    <category>semantic</category>\n    <content>User is a senior TypeScript developer with 8 years of backend experience</content>\n    <confidence>0.95</confidence>\n  </memory>\n  <memory>\n    <category>procedural</category>\n    <content>User follows TDD workflow: writes tests before implementation, runs tests after each change</content>\n    <confidence>0.88</confidence>\n  </memory>\n  <memory>\n    <category>episodic</category>\n    <content>User led database migration from MongoDB to PostgreSQL for payment system in Q2 2024</content>\n    <confidence>0.92</confidence>\n  </memory>\n</memories>";
+export declare const LONG_TERM_EXTRACTION_TEMPLATE = "# Task: Extract Long-Term Memory (Strict Criteria)\n\nYou are analyzing a conversation to extract ONLY the most critical, persistent information about the user using cognitive science memory categories.\n\n# Recent Messages\n{{recentMessages}}\n\n# Current Long-Term Memories\n{{existingMemories}}\n\n# Memory Categories (Based on Cognitive Science)\n\n## 1. EPISODIC Memory\nPersonal experiences and specific events with temporal/spatial context.\n**Examples:**\n- \"User completed migration project from MongoDB to PostgreSQL in Q2 2024\"\n- \"User encountered authentication bug in production on March 15th\"\n- \"User had a negative experience with Docker networking in previous job\"\n\n**Requirements:**\n- Must include WHO did WHAT, WHEN/WHERE\n- Must be a specific, concrete event (not a pattern)\n- Must have significant impact or relevance to future work\n\n## 2. SEMANTIC Memory\nGeneral facts, concepts, knowledge, and established truths about the user.\n**Examples:**\n- \"User is a senior backend engineer with 8 years experience\"\n- \"User specializes in distributed systems and microservices architecture\"\n- \"User's primary programming language is TypeScript\"\n- \"User works at Acme Corp as technical lead\"\n\n**Requirements:**\n- Must be factual, timeless information\n- Must be explicitly stated or demonstrated conclusively\n- No speculation or inference from single instances\n- Core identity, expertise, or knowledge only\n\n## 3. PROCEDURAL Memory\nSkills, workflows, methodologies, and how-to knowledge.\n**Examples:**\n- \"User follows strict TDD workflow: write tests first, then implementation\"\n- \"User prefers git rebase over merge to maintain linear history\"\n- \"User's debugging process: check logs \u2192 reproduce locally \u2192 binary search\"\n- \"User always writes JSDoc comments before implementing functions\"\n\n**Requirements:**\n- Must describe HOW user does something\n- Must be a repeated, consistent pattern (seen 3+ times or explicitly stated as standard practice)\n- Must be a workflow, methodology, or skill application\n- Not one-off preferences\n\n# ULTRA-STRICT EXTRACTION CRITERIA\n\n## \u2705 DO EXTRACT (Only These):\n\n**EPISODIC:**\n- Significant completed projects or milestones\n- Important bugs, incidents, or problems encountered\n- Major decisions made with lasting impact\n- Formative experiences that shape future work\n\n**SEMANTIC:**\n- Professional identity (role, title, company)\n- Core expertise and specializations (stated explicitly or demonstrated conclusively)\n- Primary languages, frameworks, or tools (not exploratory use)\n- Established facts about their work context\n\n**PROCEDURAL:**\n- Consistent workflows demonstrated 3+ times or explicitly stated\n- Standard practices user always follows\n- Methodology preferences with clear rationale\n- Debugging, testing, or development processes\n\n## \u274C NEVER EXTRACT:\n\n- **One-time requests or tasks** (e.g., \"can you generate an image\", \"help me debug this\")\n- **Casual conversations** without lasting significance\n- **Exploratory questions** (e.g., \"how does X work?\")\n- **Temporary context** (current bug, today's task)\n- **Preferences from single occurrence** (e.g., user asked for code once)\n- **Social pleasantries** (thank you, greetings)\n- **Testing or experimentation** (trying out a feature)\n- **Common patterns everyone has** (likes clear explanations)\n- **Situational information** (working on feature X today)\n- **Opinions without persistence** (single complaint, isolated praise)\n- **General knowledge** (not specific to user)\n\n# Quality Gates (ALL Must Pass)\n\n1. **Significance Test**: Will this matter in 3+ months?\n2. **Specificity Test**: Is this concrete and actionable?\n3. **Evidence Test**: Is there strong evidence (3+ instances OR explicit self-identification)?\n4. **Uniqueness Test**: Is this specific to THIS user (not generic)?\n5. **Confidence Test**: Confidence must be >= 0.85 (be VERY conservative)\n6. **Non-Redundancy Test**: Does this add NEW information not in existing memories?\n\n# Confidence Scoring (Be Conservative)\n\n- **0.95-1.0**: User explicitly stated as core identity/practice AND demonstrated multiple times\n- **0.85-0.94**: User explicitly stated OR consistently demonstrated 5+ times\n- **0.75-0.84**: Strong pattern (3-4 instances) with supporting context\n- **Below 0.75**: DO NOT EXTRACT (insufficient evidence)\n\n# Critical Instructions\n\n1. **Default to NOT extracting** - When in doubt, skip it\n2. **Require overwhelming evidence** - One or two mentions is NOT enough\n3. **Focus on what's PERSISTENT** - Not what's temporary or situational\n4. **Verify against existing memories** - Don't duplicate or contradict\n5. **Maximum 2-3 extractions per run** - Quality over quantity\n\n**If there are no qualifying facts (which is common), respond with <memories></memories>**\n\n# Response Format\n\n<memories>\n  <memory>\n    <category>semantic</category>\n    <content>User is a senior TypeScript developer with 8 years of backend experience</content>\n    <confidence>0.95</confidence>\n  </memory>\n  <memory>\n    <category>procedural</category>\n    <content>User follows TDD workflow: writes tests before implementation, runs tests after each change</content>\n    <confidence>0.88</confidence>\n  </memory>\n  <memory>\n    <category>episodic</category>\n    <content>User led database migration from MongoDB to PostgreSQL for payment system in Q2 2024</content>\n    <confidence>0.92</confidence>\n  </memory>\n</memories>";
+export declare const updateSummarizationTemplate = "# Task: Update and Condense Conversation Summary\n\nYou are updating an existing conversation summary with new messages, while keeping the total summary concise.\n\n# Existing Summary\n{{existingSummary}}\n\n# Existing Topics\n{{existingTopics}}\n\n# New Messages Since Last Summary\n{{newMessages}}\n\n# Instructions\nUpdate the summary by:\n1. Merging the existing summary with insights from the new messages\n2. Removing redundant or less important details to stay under the token limit\n3. Keeping the most important context and decisions\n4. Adding new topics if they emerge\n5. **CRITICAL**: Keep the ENTIRE updated summary under 2500 tokens\n\nThe goal is a rolling summary that captures the essence of the conversation without growing indefinitely.\n\nRespond in this XML format:\n<summary>\n  <text>Your updated and condensed summary here</text>\n  <topics>topic1, topic2, topic3</topics>\n  <keyPoints>\n    <point>First key point</point>\n    <point>Second key point</point>\n  </keyPoints>\n</summary>";
+export declare const UPDATE_SUMMARIZATION_TEMPLATE = "# Task: Update and Condense Conversation Summary\n\nYou are updating an existing conversation summary with new messages, while keeping the total summary concise.\n\n# Existing Summary\n{{existingSummary}}\n\n# Existing Topics\n{{existingTopics}}\n\n# New Messages Since Last Summary\n{{newMessages}}\n\n# Instructions\nUpdate the summary by:\n1. Merging the existing summary with insights from the new messages\n2. Removing redundant or less important details to stay under the token limit\n3. Keeping the most important context and decisions\n4. Adding new topics if they emerge\n5. **CRITICAL**: Keep the ENTIRE updated summary under 2500 tokens\n\nThe goal is a rolling summary that captures the essence of the conversation without growing indefinitely.\n\nRespond in this XML format:\n<summary>\n  <text>Your updated and condensed summary here</text>\n  <topics>topic1, topic2, topic3</topics>\n  <keyPoints>\n    <point>First key point</point>\n    <point>Second key point</point>\n  </keyPoints>\n</summary>";
+//# sourceMappingURL=prompts.d.ts.map

package/dist/generated/prompts/typescript/prompts.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"prompts.d.ts","sourceRoot":"","sources":["../../../../src/generated/prompts/typescript/prompts.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAEH,eAAO,MAAM,4BAA4B,25BA6B9B,CAAC;AAEZ,eAAO,MAAM,8BAA8B,25BAA+B,CAAC;AAE3E,eAAO,MAAM,0BAA0B,q7KAoI3B,CAAC;AAEb,eAAO,MAAM,6BAA6B,q7KAA6B,CAAC;AAExE,eAAO,MAAM,2BAA2B,0/BA+B7B,CAAC;AAEZ,eAAO,MAAM,6BAA6B,0/BAA8B,CAAC"}

package/dist/index.d.ts

@@ -1,41 +1,9 @@
-import type { Plugin } from '@elizaos/core';
-export * from './types/index';
-export * from './schemas/index';
-export { MemoryService } from './services/memory-service';
-export { contextSummaryProvider } from './providers/context-summary';
-export { recentMessagesProvider } from './providers/recent-messages';
-export { longTermMemoryProvider } from './providers/long-term-memory';
-/**
- * Memory Plugin
- *
- * Advanced memory management plugin that provides:
- *
- * **Short-term Memory (Conversation Summarization)**:
- * - Automatically summarizes long conversations to reduce context size
- * - Retains recent messages while archiving older ones as summaries
- * - Configurable thresholds for when to summarize
- *
- * **Long-term Memory (Persistent Facts)**:
- * - Extracts and stores persistent facts about users
- * - Categorizes information (identity, expertise, preferences, etc.)
- * - Provides context-aware user profiles across all conversations
- *
- * **Components**:
- * - `MemoryService`: Manages all memory operations
- * - Evaluators: Process conversations to create summaries and extract facts
- * - Providers: Inject memory context into conversations
- * - Actions: Allow manual memory storage via user commands
- *
- * **Configuration** (via environment variables):
- * - `MEMORY_SUMMARIZATION_THRESHOLD`: Messages before summarization (default: 50)
- * - `MEMORY_RETAIN_RECENT`: Recent messages to keep (default: 10)
- * - `MEMORY_LONG_TERM_ENABLED`: Enable long-term extraction (default: true)
- * - `MEMORY_CONFIDENCE_THRESHOLD`: Minimum confidence to store (default: 0.7)
- *
- * **Database Tables**:
- * - `long_term_memories`: Persistent user facts
- * - `session_summaries`: Conversation summaries
- * - `memory_access_logs`: Optional usage tracking
- */
+import type { Plugin } from "@elizaos/core";
+export { longTermExtractionEvaluator, summarizationEvaluator, } from "./evaluators";
+export { contextSummaryProvider, longTermMemoryProvider } from "./providers";
+export * from "./schemas";
+export { MemoryService } from "./services/memory-service";
+export * from "./types";
 export declare const memoryPlugin: Plugin;
 export default memoryPlugin;
+//# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,eAAe,CAAC;AAM5C,OAAO,EACL,2BAA2B,EAC3B,sBAAsB,GACvB,MAAM,cAAc,CAAC;AACtB,OAAO,EAAE,sBAAsB,EAAE,sBAAsB,EAAE,MAAM,aAAa,CAAC;AAC7E,cAAc,WAAW,CAAC;AAC1B,OAAO,EAAE,aAAa,EAAE,MAAM,2BAA2B,CAAC;AAC1D,cAAc,SAAS,CAAC;AAExB,eAAO,MAAM,YAAY,EAAE,MAW1B,CAAC;AAEF,eAAe,YAAY,CAAC"}