@juspay/neurolink 13.8.15 → 13.8.16

package/dist/core/conversationMemoryFactory.d.ts

@@ -2,13 +2,13 @@
  * Conversation Memory Factory for NeuroLink
  * Creates appropriate conversation memory manager based on configuration
  */
-import type { StorageType, ConversationMemoryConfig, RedisStorageConfig } from "../types/index.js";
+import type { StorageType, ConversationMemoryConfig, NeuroLinkEvents, RedisStorageConfig, TypedEventEmitter } from "../types/index.js";
 import { ConversationMemoryManager } from "./conversationMemoryManager.js";
 import { RedisConversationMemoryManager } from "./redisConversationMemoryManager.js";
 /**
  * Creates a conversation memory manager based on configuration
  */
-export declare function createConversationMemoryManager(config: ConversationMemoryConfig, storageType?: StorageType, redisConfig?: RedisStorageConfig): ConversationMemoryManager | RedisConversationMemoryManager;
+export declare function createConversationMemoryManager(config: ConversationMemoryConfig, storageType?: StorageType, redisConfig?: RedisStorageConfig, eventEmitter?: TypedEventEmitter<NeuroLinkEvents>): ConversationMemoryManager | RedisConversationMemoryManager;
 /**
  * Get storage type from environment variable or configuration
  */

package/dist/core/conversationMemoryFactory.js

@@ -8,7 +8,7 @@ import { RedisConversationMemoryManager } from "./redisConversationMemoryManager
 /**
  * Creates a conversation memory manager based on configuration
  */
-export function createConversationMemoryManager(config, storageType = "memory", redisConfig) {
+export function createConversationMemoryManager(config, storageType = "memory", redisConfig, eventEmitter) {
     logger.debug("[conversationMemoryFactory] Creating conversation memory manager", {
         storageType,
         config: {
@@ -38,7 +38,7 @@ export function createConversationMemoryManager(config, storageType = "memory",
             ttl: redisConfig?.ttl || 86400,
             hasConnectionOptions: !!redisConfig?.connectionOptions,
         });
-        const redisManager = new RedisConversationMemoryManager(config, redisConfig);
+        const redisManager = new RedisConversationMemoryManager(config, redisConfig, eventEmitter);
         logger.debug("[conversationMemoryFactory] Redis conversation manager created successfully", {
             managerType: redisManager.constructor.name,
             config: {

package/dist/core/conversationMemoryInitializer.d.ts

@@ -2,7 +2,7 @@
  * Conversation Memory Initializer
  * Provides integration with Redis storage for conversation memory
  */
-import type { ConversationMemoryConfig } from "../types/index.js";
+import type { ConversationMemoryConfig, NeuroLinkEvents, TypedEventEmitter } from "../types/index.js";
 import type { ConversationMemoryManager } from "./conversationMemoryManager.js";
 import type { RedisConversationMemoryManager } from "./redisConversationMemoryManager.js";
 /**
@@ -11,4 +11,4 @@ import type { RedisConversationMemoryManager } from "./redisConversationMemoryMa
  */
 export declare function initializeConversationMemory(config?: {
     conversationMemory?: Partial<ConversationMemoryConfig>;
-}): Promise<ConversationMemoryManager | RedisConversationMemoryManager | null>;
+}, eventEmitter?: TypedEventEmitter<NeuroLinkEvents>): Promise<ConversationMemoryManager | RedisConversationMemoryManager | null>;

package/dist/core/conversationMemoryInitializer.js

@@ -9,7 +9,7 @@ import { createConversationMemoryManager, getRedisConfigFromEnv, getStorageType,
  * Initialize conversation memory for NeuroLink
  * This function decides whether to use in-memory or Redis storage
  */
-export async function initializeConversationMemory(config) {
+export async function initializeConversationMemory(config, eventEmitter) {
     logger.debug("[conversationMemoryInitializer] Initialize conversation memory called", {
         hasConfig: !!config,
         hasMemoryConfig: !!config?.conversationMemory,
@@ -58,7 +58,7 @@ export async function initializeConversationMemory(config) {
             });
             // Create Redis-based conversation memory manager
             logger.debug("[conversationMemoryInitializer] Creating Redis conversation memory manager");
-            const redisMemoryManager = createConversationMemoryManager(memoryConfig, "redis", redisConfig);
+            const redisMemoryManager = createConversationMemoryManager(memoryConfig, "redis", redisConfig, eventEmitter);
             logger.debug("[conversationMemoryInitializer] Checking Redis manager creation result", {
                 managerType: redisMemoryManager?.constructor?.name || "unknown",
                 isRedisType: redisMemoryManager?.constructor?.name ===

package/dist/core/redisConversationMemoryManager.d.ts

@@ -2,7 +2,7 @@
  * Redis Conversation Memory Manager for NeuroLink
  * Redis-based implementation of conversation storage with same interface as ConversationMemoryManager
  */
-import type { ChatMessage, ConversationMemoryConfig, ConversationMemoryStats, RedisConversationObject, RedisStorageConfig, SessionListItem, SessionMemory, SessionMetadata, StoreConversationTurnOptions, AgenticLoopReportMetadata, IConversationMemoryManager } from "../types/index.js";
+import type { ChatMessage, ConversationMemoryConfig, ConversationMemoryStats, RedisConversationObject, RedisStorageConfig, SessionListItem, SessionMemory, SessionMetadata, StoreConversationTurnOptions, AgenticLoopReportMetadata, IConversationMemoryManager, NeuroLinkEvents, TypedEventEmitter } from "../types/index.js";
 /**
  * Redis-based implementation of the ConversationMemoryManager
  * Uses the same interface but stores data in Redis
@@ -13,6 +13,11 @@ export declare class RedisConversationMemoryManager implements IConversationMemo
     private summarizationEngine;
     private redisConfig;
     private redisClient;
+    /**
+     * Receives `conversation:titleGenerated` once a new conversation's title is
+     * stored. Optional because the manager can be constructed standalone.
+     */
+    private readonly eventEmitter?;
     /**
      * Temporary storage for tool execution data to prevent race conditions
      * Key format: "${sessionId}:${userId}"
@@ -28,7 +33,7 @@ export declare class RedisConversationMemoryManager implements IConversationMemo
      * Key format: "${sessionId}:${userId}"
      */
     private summarizationInProgress;
-    constructor(config: ConversationMemoryConfig, redisConfig?: RedisStorageConfig);
+    constructor(config: ConversationMemoryConfig, redisConfig?: RedisStorageConfig, eventEmitter?: TypedEventEmitter<NeuroLinkEvents>);
     /**
      * Initialize the memory manager with Redis connection
      */
@@ -155,6 +160,12 @@ export declare class RedisConversationMemoryManager implements IConversationMemo
      * @returns Complete conversation object with all data, or null if session doesn't exist
      */
     getUserSessionObject(userId: string, sessionId: string): Promise<RedisConversationObject | null>;
+    /**
+     * Announce a stored title. A throwing listener is logged rather than
+     * propagated: the title is already persisted, and the caller's catch block
+     * reports title-generation failures.
+     */
+    private emitTitleGenerated;
     /**
      * Generate a conversation title from the first user message
      * Uses AI to create a concise, descriptive title (5-8 words)

package/dist/core/redisConversationMemoryManager.js

@@ -29,6 +29,11 @@ export class RedisConversationMemoryManager {
     summarizationEngine = new SummarizationEngine();
     redisConfig;
     redisClient = null;
+    /**
+     * Receives `conversation:titleGenerated` once a new conversation's title is
+     * stored. Optional because the manager can be constructed standalone.
+     */
+    eventEmitter;
     /**
      * Temporary storage for tool execution data to prevent race conditions
      * Key format: "${sessionId}:${userId}"
@@ -44,9 +49,10 @@ export class RedisConversationMemoryManager {
      * Key format: "${sessionId}:${userId}"
      */
     summarizationInProgress = new Set();
-    constructor(config, redisConfig = {}) {
+    constructor(config, redisConfig = {}, eventEmitter) {
         this.config = config;
         this.redisConfig = getNormalizedConfig(redisConfig);
+        this.eventEmitter = eventEmitter;
     }
     /**
      * Initialize the memory manager with Redis connection
@@ -419,6 +425,12 @@ export class RedisConversationMemoryManager {
                                 const serializedData = serializeConversation(updatedConversation);
                                 if (this.redisClient) {
                                     await setWithTtl(this.redisClient, updatedRedisKey, serializedData, this.redisConfig.ttl);
+                                    this.emitTitleGenerated({
+                                        sessionId: options.sessionId,
+                                        userId: normalizedUserId,
+                                        title,
+                                        timestamp: Date.now(),
+                                    });
                                 }
                             }
                         }
@@ -1023,6 +1035,24 @@ export class RedisConversationMemoryManager {
             return null;
         }
     }
+    /**
+     * Announce a stored title. A throwing listener is logged rather than
+     * propagated: the title is already persisted, and the caller's catch block
+     * reports title-generation failures.
+     */
+    emitTitleGenerated(event) {
+        try {
+            this.eventEmitter?.emit("conversation:titleGenerated", event);
+        }
+        catch (listenerError) {
+            logger.warn("[RedisConversationMemoryManager] conversation:titleGenerated listener threw", {
+                sessionId: event.sessionId,
+                error: listenerError instanceof Error
+                    ? listenerError.message
+                    : String(listenerError),
+            });
+        }
+    }
     /**
      * Generate a conversation title from the first user message
      * Uses AI to create a concise, descriptive title (5-8 words)

package/dist/neurolink.js

@@ -13851,7 +13851,7 @@ Current user's request: ${currentInput}`;
             // Import the integration module
             const { initializeConversationMemory } = await import("./core/conversationMemoryInitializer.js");
             // Use the integration module to create the appropriate memory manager
-            const memoryManager = await initializeConversationMemory(this.conversationMemoryConfig);
+            const memoryManager = await initializeConversationMemory(this.conversationMemoryConfig, this.emitter);
             // Assign to conversationMemory with proper type to handle both memory manager types
             this.conversationMemory = memoryManager;
             // Reset the lazy init flag since we've now initialized

package/dist/types/common.d.ts

@@ -2,7 +2,7 @@
  * Common utility types for NeuroLink
  */
 import type { NeuroLink } from "../neurolink.js";
-import type { ConversationMemoryConfig } from "./conversation.js";
+import type { ConversationMemoryConfig, ConversationTitleGeneratedEvent } from "./conversation.js";
 import type { AutoresearchErrorEvent, AutoresearchExperimentCompletedEvent, AutoresearchExperimentStartedEvent, AutoresearchInitializedEvent, AutoresearchMetricImprovedEvent, AutoresearchPhaseChangedEvent, AutoresearchResumedEvent, AutoresearchRevertEvent, AutoresearchRevertFailedEvent, AutoresearchStateUpdatedEvent } from "./autoresearch.js";
 /**
  * Type-safe unknown value - use when type is truly unknown
@@ -120,6 +120,7 @@ export type NeuroLinkEvents = {
     "externalMCP:serverRemoved": unknown;
     "tools-register:start": unknown;
     "tools-register:end": unknown;
+    "conversation:titleGenerated": ConversationTitleGeneratedEvent;
     connected: unknown;
     message: unknown;
     error: unknown;

package/dist/types/conversation.d.ts

@@ -752,6 +752,18 @@ export type RedisConversationObject = ConversationBase & {
     /** Array of conversation messages */
     messages: ChatMessage[];
 };
+/**
+ * Payload of the `conversation:titleGenerated` event, emitted once the title
+ * of a new Redis-backed conversation has been stored.
+ */
+export type ConversationTitleGeneratedEvent = {
+    sessionId: string;
+    userId: string;
+    /** The title that was stored, which is what `listSessions()` reports. */
+    title: string;
+    /** Unix epoch milliseconds when the title was stored. */
+    timestamp: number;
+};
 /**
  * Full conversation data for session restoration and manipulation
  * Extends Redis storage object with additional loop mode metadata

package/docs-site/static/search-index.json

@@ -8466,15 +8466,16 @@
 {"objectID":"156003cd4819e4dbb7f346be7120ea605e8ad136ca867e2f736327744c48c281","title":"2. Best Practices","url":"/docs/mcp/testing#2-best-practices","content":"Use TypeScript for full type safety\nValidate inputs with Zod schemas\nHandle errors gracefully in tools\nLog execution for debugging\nTest thoroughly before deployment","hierarchy":{"lvl0":"Mcp","lvl1":"🧪 MCP Foundation Testing Guide","lvl2":"2. Best Practices","lvl3":""}},
 {"objectID":"e772b5dca6bea98f96f9043b173ee610272e201d08879869318c2d8070425ffc","title":"3. Performance Monitoring","url":"/docs/mcp/testing#3-performance-monitoring","content":"3. Performance Monitoring","hierarchy":{"lvl0":"Mcp","lvl1":"🧪 MCP Foundation Testing Guide","lvl2":"3. Performance Monitoring","lvl3":""}},
 {"objectID":"82c7cc03c75290cac4197443132e907f9796ad297a7a81df29ac6e5ae9c42734","title":"🚀 Next Steps","url":"/docs/mcp/testing#-next-steps","content":"✅ Test Current Implementation - Use programmatic testing examples\n🔧 Add CLI Integration - Implement MCP CLI commands\n🏗️ Create Custom Servers - Build domain-specific tool servers\n📊 Monitor Performance - Track tool execution and usage\n🔄 Iterate and Improve - Enhance based on real usage\n\nMCP Foundation is production-ready and waiting for your custom tools! 🎉","hierarchy":{"lvl0":"Mcp","lvl1":"🧪 MCP Foundation Testing Guide","lvl2":"🚀 Next Steps","lvl3":""}},
-{"objectID":"d287e2ebab877225d0b71aafb45118dd2b1d04914f8cf4cd8b2c82b12aba80b8","title":"Conversation Memory","url":"/docs/memory/conversation","content":"Conversation Memory\n\nNeuroLink's Conversation Memory feature enables AI models to maintain context across multiple turns within a session, creating more natural and coherent conversations.\n\n🧠 Overview\n\nThe conversation memory system provides:\nSession-based memory: Each conversation session maintains its own context\nTurn-by-turn persistence: AI remembers previous messages within a session\nAutomatic cleanup: Configurable limits to prevent memory bloat\nSession isolation: Different sessions don't interfere with each other\nIn-memory storage: Fast, lightweight storage for conversation history\nUniversal Method Support: Works seamlessly with both generate() and stream() methods\nStream Integration: Full conversation memory support for streaming responses\n\n⚙️ Configuration\n\nEnvironment Variables\n\nProgrammatic Configuration\n\n🚀 Usage Examples\n\nBasic Usage with Session ID\n\nStreaming Support\n\nThe conversation memory system now fully supports streaming responses with the same memory persistence:\n\nMixed Generate/Stream Conversations\n\nYou can seamlessly mix generate() and stream() calls within the same conversation:\n\nSession Isolation Example\n\n📊 Memory Management\n\nTurn Limits\n\nWhen the number of conversation turns exceeds maxTurnsPerSession, older messages are automatically removed:\n\nSession Limits\n\nWhen the number of active sessions exceeds maxSessions, the least recently used sessions are removed:\n\n🔌 API Reference\n\nMemory Statistics\n\nSession Management\n\n🧪 Test Results\n\nThe conversation memory system has been thoroughly tested and validated:\n\n✅ Test Suite Results\n\n| Test Case             | Status  | Description                                     |\n| --------------------- | ------- | ----------------------------------------------- |\n| Basic Memory      | ✅ PASS | AI correctly remembers information across turns |\n| Session Isolation | ✅ PASS | Sessions remain completely separate             |\n| Turn Limits       | ✅ PASS | Automatic cleanup when limits exceeded          |\n| Session Limits    | ✅ PASS | LRU eviction of old sessions                    |\n| API Functions     | ✅ PASS | Clear operations work correctly                 |\n\nExample Test Output\n\n💡 Best Practices\nSession ID Strategy\nMemory Limits\nError Handling\n\n🔧 Technical Implementation\n\nArchitecture\n\nMessage Format\n\n🔍 Troubleshooting\n\nCommon Issues\n\nMemory not persisting between calls\nEnsure sessionId is consistent across calls\nVerify conversationMemory.enabled is true\nCheck that sessionId is a valid string\n\nPerformance issues with large conversations\nReduce maxTurnsPerSession limit\nImplement session cleanup strategies\nMonitor memory usage statistics\n\nSession isolation not working\nVerify different sessionId values are being used\nCheck for session ID conflicts or duplicates\n\nDebug Logging\n\n🔗 Related Documentation\nRedis Conversation Export - Export session history as JSON for analytics\nAPI Reference - Complete SDK documentation\nConfiguration - Environment setup guide\nExamples - More usage examples\nTesting Guide - How to test conversation memory\n\n📈 Performance Characteristics\nMemory Usage: ~1KB per conversation turn\nLookup Time: O(1) for session retrieval\nCleanup Time: O(n) for session limit enforcement\nConcurrency: Thread-safe in-memory operations\n\nThe conversation memory system is designed for production use with efficient memory management and robust error handling.","hierarchy":{"lvl0":"Memory","lvl1":"Conversation Memory","lvl2":"","lvl3":""}},
+{"objectID":"d287e2ebab877225d0b71aafb45118dd2b1d04914f8cf4cd8b2c82b12aba80b8","title":"Conversation Memory","url":"/docs/memory/conversation","content":"Conversation Memory\n\nNeuroLink's Conversation Memory feature enables AI models to maintain context across multiple turns within a session, creating more natural and coherent conversations.\n\n🧠 Overview\n\nThe conversation memory system provides:\nSession-based memory: Each conversation session maintains its own context\nTurn-by-turn persistence: AI remembers previous messages within a session\nAutomatic cleanup: Configurable limits to prevent memory bloat\nSession isolation: Different sessions don't interfere with each other\nIn-memory storage: Fast, lightweight storage for conversation history\nUniversal Method Support: Works seamlessly with both generate() and stream() methods\nStream Integration: Full conversation memory support for streaming responses\nTitle Generation Events: Redis-backed conversations get an AI-generated title, announced with a conversation:titleGenerated event\n\n⚙️ Configuration\n\nEnvironment Variables\n\nProgrammatic Configuration\n\n🚀 Usage Examples\n\nBasic Usage with Session ID\n\nStreaming Support\n\nThe conversation memory system now fully supports streaming responses with the same memory persistence:\n\nMixed Generate/Stream Conversations\n\nYou can seamlessly mix generate() and stream() calls within the same conversation:\n\nSession Isolation Example\n\n🏷️ Title Generation Events {#title-generation-events}\n\nWhen a Redis-backed conversation stores its first turn, NeuroLink generates a title for it in the background and saves it on the session (listSessions() reports it). Once the title is stored, the SDK's event emitter fires conversation:titleGenerated.\n\nPayload (ConversationTitleGeneratedEvent):\n\n| Property    | Type     | Description                                          |\n| ----------- | -------- | ---------------------------------------------------- |\n| sessionId | string | Session the title belongs to                         |\n| userId    | string | User that owns the session (randomUser when unset) |\n| title     | string | The title that was stored                            |\n| timestamp | number | Unix epoch milliseconds when the title was stored    |\n\nNotes:\nThe event fires once per conversation, on the first turn, not on later turns.\nOnly Redis-backed memory generates titles; in-memory storage lists sessions by session ID.\nIf the summarization provider cannot answer, the stored title falls back to the first 30 characters of the message plus ..., and the event carries that fallback.\nSet NEUROLINK_TITLE_PROMPT to customize the title prompt. ${userMessage} is replaced with the user's message.\n\n📊 Memory Management\n\nTurn Limits\n\nWhen the number of conversation turns exceeds maxTurnsPerSession, older messages are automatically removed:\n\nSession Limits\n\nWhen the number of active sessions exceeds maxSessions, the least recently used sessions are removed:\n\n🔌 API Reference\n\nMemory Statistics\n\nSession Management\n\n🧪 Test Results\n\nThe conversation memory system has been thoroughly tested and validated:\n\n✅ Test Suite Results\n\n| Test Case             | Status  | Description                                     |\n| --------------------- | ------- | ----------------------------------------------- |\n| Basic Memory      | ✅ PASS | AI correctly remembers information across turns |\n| Session Isolation | ✅ PASS | Sessions remain completely separate             |\n| Turn Limits       | ✅ PASS | Automatic cleanup when limits exceeded          |\n| Session Limits    | ✅ PASS | LRU eviction of old sessions                    |\n| API Functions     | ✅ PASS | Clear operations work correctly                 |\n\nExample Test Output\n\n💡 Best Practices\nSession ID Strategy\nMemory Limits\nError Handling\n\n🔧 Technical Implementation\n\nArchitecture\n\nMessage Format\n\n🔍 Troubleshooting\n\nCommon Issues\n\nMemory not persisting between calls\nEnsure sessionId is consistent across calls\nVerify conversationMemory.enabled is true\nCheck that sessionId is a valid string\n\nPerformance issues with large conversations\nReduce maxTurnsPerSession limit\nImplement session cleanup strategies\nMonitor memory usage statistics\n\nSession isolation not working\nVerify different sessionId values are being used\nCheck for session ID conflicts or duplicates\n\nDebug Logging\n\n🔗 Related Documentation\nRedis Conversation Export - Export session history as JSON for analytics\nAPI Reference - Complete SDK documentation\nConfiguration - Environment setup guide\nExamples - More usage examples\nTesting Guide - How to test conversation memory\n\n📈 Performance Characteristics\nMemory Usage: ~1KB per conversation turn\nLookup Time: O(1) for session retrieval\nCleanup Time: O(n) for session limit enforcement\nConcurrency: Thread-safe in-memory operations\n\nThe conversation memory system is designed for production use with efficient memory management and robust error handling.","hierarchy":{"lvl0":"Memory","lvl1":"Conversation Memory","lvl2":"","lvl3":""}},
 {"objectID":"c5ecb284a686db95e36732c07ddc3b49949d9113b826193e1f6feabf1ae48784","title":"Conversation Memory","url":"/docs/memory/conversation#conversation-memory","content":"NeuroLink's Conversation Memory feature enables AI models to maintain context across multiple turns within a session, creating more natural and coherent conversations.","hierarchy":{"lvl0":"Memory","lvl1":"Conversation Memory","lvl2":"Conversation Memory","lvl3":""}},
-{"objectID":"5eb7e9215a286dcd5f45287f758f7c7aa08263f946d3b58182bd9ae2ea029d98","title":"🧠 Overview","url":"/docs/memory/conversation#-overview","content":"The conversation memory system provides:\nSession-based memory: Each conversation session maintains its own context\nTurn-by-turn persistence: AI remembers previous messages within a session\nAutomatic cleanup: Configurable limits to prevent memory bloat\nSession isolation: Different sessions don't interfere with each other\nIn-memory storage: Fast, lightweight storage for conversation history\nUniversal Method Support: Works seamlessly with both generate() and stream() methods\nStream Integration: Full conversation memory support for streaming responses","hierarchy":{"lvl0":"Memory","lvl1":"Conversation Memory","lvl2":"🧠 Overview","lvl3":""}},
+{"objectID":"5eb7e9215a286dcd5f45287f758f7c7aa08263f946d3b58182bd9ae2ea029d98","title":"🧠 Overview","url":"/docs/memory/conversation#-overview","content":"The conversation memory system provides:\nSession-based memory: Each conversation session maintains its own context\nTurn-by-turn persistence: AI remembers previous messages within a session\nAutomatic cleanup: Configurable limits to prevent memory bloat\nSession isolation: Different sessions don't interfere with each other\nIn-memory storage: Fast, lightweight storage for conversation history\nUniversal Method Support: Works seamlessly with both generate() and stream() methods\nStream Integration: Full conversation memory support for streaming responses\nTitle Generation Events: Redis-backed conversations get an AI-generated title, announced with a conversation:titleGenerated event","hierarchy":{"lvl0":"Memory","lvl1":"Conversation Memory","lvl2":"🧠 Overview","lvl3":""}},
 {"objectID":"d2eb5a1a0caa1a4c9a75e15f0cf37e5cd1f37e00d9ef168bac48c0db9cb40ffd","title":"Environment Variables","url":"/docs/memory/conversation#environment-variables","content":"Environment Variables","hierarchy":{"lvl0":"Memory","lvl1":"Conversation Memory","lvl2":"Environment Variables","lvl3":""}},
 {"objectID":"520e090e02894dc26d3732e6e5710332a0c681ebd3f9648f421d48e01c991d65","title":"Programmatic Configuration","url":"/docs/memory/conversation#programmatic-configuration","content":"Programmatic Configuration","hierarchy":{"lvl0":"Memory","lvl1":"Conversation Memory","lvl2":"Programmatic Configuration","lvl3":""}},
 {"objectID":"75f91f33db6fd6704adb0d78885dafb7f3d33a0e36ac5edd543ed070cacd2329","title":"Basic Usage with Session ID","url":"/docs/memory/conversation#basic-usage-with-session-id","content":"Basic Usage with Session ID","hierarchy":{"lvl0":"Memory","lvl1":"Conversation Memory","lvl2":"Basic Usage with Session ID","lvl3":""}},
 {"objectID":"5d65f1e509ac96cb91a4a3027345c19b33198f0e3dd51442e5f3ef4d5e6bf8ba","title":"Streaming Support","url":"/docs/memory/conversation#streaming-support","content":"The conversation memory system now fully supports streaming responses with the same memory persistence:","hierarchy":{"lvl0":"Memory","lvl1":"Conversation Memory","lvl2":"Streaming Support","lvl3":""}},
 {"objectID":"b104538f38fc8e518c4b440d352a6888ccbc0e3fe334446b317e81ef2815ef69","title":"Mixed Generate/Stream Conversations","url":"/docs/memory/conversation#mixed-generatestream-conversations","content":"You can seamlessly mix generate() and stream() calls within the same conversation:","hierarchy":{"lvl0":"Memory","lvl1":"Conversation Memory","lvl2":"Mixed Generate/Stream Conversations","lvl3":""}},
 {"objectID":"3d44a6a1ef6c03c6f48aabb0c9516e1f05d660eac1d51829bfaf2e8506bd9c2e","title":"Session Isolation Example","url":"/docs/memory/conversation#session-isolation-example","content":"Session Isolation Example","hierarchy":{"lvl0":"Memory","lvl1":"Conversation Memory","lvl2":"Session Isolation Example","lvl3":""}},
+{"objectID":"778e79ba226a658a91d70c69514a873920f93d560c695eb75e1d9b6a735567a8","title":"🏷️ Title Generation Events","url":"/docs/memory/conversation#title-generation-events","content":"When a Redis-backed conversation stores its first turn, NeuroLink generates a title for it in the background and saves it on the session (listSessions() reports it). Once the title is stored, the SDK's event emitter fires conversation:titleGenerated.\n\nPayload (ConversationTitleGeneratedEvent):\n\n| Property    | Type     | Description                                          |\n| ----------- | -------- | ---------------------------------------------------- |\n| sessionId | string | Session the title belongs to                         |\n| userId    | string | User that owns the session (randomUser when unset) |\n| title     | string | The title that was stored                            |\n| timestamp | number | Unix epoch milliseconds when the title was stored    |\n\nNotes:\nThe event fires once per conversation, on the first turn, not on later turns.\nOnly Redis-backed memory generates titles; in-memory storage lists sessions by session ID.\nIf the summarization provider cannot answer, the stored title falls back to the first 30 characters of the message plus ..., and the event carries that fallback.\nSet NEUROLINK_TITLE_PROMPT to customize the title prompt. ${userMessage} is replaced with the user's message.","hierarchy":{"lvl0":"Memory","lvl1":"Conversation Memory","lvl2":"🏷️ Title Generation Events","lvl3":""}},
 {"objectID":"63f2feb8c208abf16abfab0606af7eb1d9d51bcbc584182610a3d692a41ef777","title":"Turn Limits","url":"/docs/memory/conversation#turn-limits","content":"When the number of conversation turns exceeds maxTurnsPerSession, older messages are automatically removed:","hierarchy":{"lvl0":"Memory","lvl1":"Conversation Memory","lvl2":"Turn Limits","lvl3":""}},
 {"objectID":"211814691635003dcae6fae6c3c3e7cb5b400ba93b6f4ad45fdec9423659ec0c","title":"Session Limits","url":"/docs/memory/conversation#session-limits","content":"When the number of active sessions exceeds maxSessions, the least recently used sessions are removed:","hierarchy":{"lvl0":"Memory","lvl1":"Conversation Memory","lvl2":"Session Limits","lvl3":""}},
 {"objectID":"11e00a73bb57324fcdab4d4130bf0f98bb4cb3b754b4e558e2feb4474e73a1d3","title":"Memory Statistics","url":"/docs/memory/conversation#memory-statistics","content":"Memory Statistics","hierarchy":{"lvl0":"Memory","lvl1":"Conversation Memory","lvl2":"Memory Statistics","lvl3":""}},
@@ -10349,6 +10350,7 @@
 {"objectID":"d79631a303031924a7185daa0471458026c9d9ef6bee4a13e49d9ce0610262b9","title":"Event System","url":"/docs/sdk/api-reference#event-system","content":"NeuroLink emits events throughout the generation and streaming lifecycle through a TypedEventEmitter. NeuroLink does not extend EventEmitter itself, so there is no neurolink.on(): get the emitter with getEventEmitter(), subscribe with on() and unsubscribe with off().","hierarchy":{"lvl0":"Sdk","lvl1":"API Reference","lvl2":"Event System","lvl3":""}},
 {"objectID":"357bbb718f458d764e00524826a1d42a64da83167df93a52c04d9ddec3651764","title":"Core Events","url":"/docs/sdk/api-reference#core-events","content":"| Event              | Emitted When                         |\n| ------------------ | ------------------------------------ |\n| generation:start | A generate() call begins           |\n| generation:end   | A generate() call completes        |\n| stream:start     | A stream() call begins             |\n| stream:chunk     | A new chunk arrives during streaming |\n| stream:end       | Streaming completes normally         |\n| stream:complete  | Stream fully consumed                |\n| stream:error     | An error occurs during streaming     |\n| tool:start       | A tool execution begins              |\n| tool:end         | A tool execution completes           |\n| response:start   | A provider response begins           |\n| response:end     | A provider response completes        |","hierarchy":{"lvl0":"Sdk","lvl1":"API Reference","lvl2":"Core Events","lvl3":""}},
 {"objectID":"efcf19aa651c13dbc72ef4b3d0f83986ee180008a076c0db030509880e4d4b1a","title":"MCP Server Events","url":"/docs/sdk/api-reference#mcp-server-events","content":"| Event                            | Emitted When                              |\n| -------------------------------- | ----------------------------------------- |\n| externalMCP:serverConnected    | An external MCP server connects           |\n| externalMCP:serverDisconnected | An external MCP server disconnects        |\n| externalMCP:serverFailed       | An external MCP server connection fails   |\n| externalMCP:toolDiscovered     | A new tool is discovered on an MCP server |\n| externalMCP:toolRemoved        | A tool is removed from an MCP server      |\n| externalMCP:serverAdded        | A new MCP server registration is added    |\n| externalMCP:serverRemoved      | An MCP server registration is removed     |","hierarchy":{"lvl0":"Sdk","lvl1":"API Reference","lvl2":"MCP Server Events","lvl3":""}},
+{"objectID":"e6691df9653e15f2a7a988af6dbe15f86784234b7aa7030fa74880e053d1e262","title":"Conversation Memory Events","url":"/docs/sdk/api-reference#conversation-memory-events","content":"| Event                         | Emitted When                                                                                                                     |\n| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |\n| conversation:titleGenerated | A new Redis-backed conversation's title is stored (see Conversation Memory) |","hierarchy":{"lvl0":"Sdk","lvl1":"API Reference","lvl2":"Conversation Memory Events","lvl3":""}},
 {"objectID":"c4d157804d0d96f1d8571e6aabeff4305aca0c07c151894dee3804d611331de6","title":"Other Events","url":"/docs/sdk/api-reference#other-events","content":"| Event                  | Emitted When                        |\n| ---------------------- | ----------------------------------- |\n| tools-register:start | Tool registration process begins    |\n| tools-register:end   | Tool registration process completes |\n| connected            | Connection established              |\n| message              | General message event               |\n| error                | An error occurs                     |\n| log                  | A log message is emitted            |\n| log-event            | A structured log event is emitted   |\n\nTypedEventEmitter Interface:","hierarchy":{"lvl0":"Sdk","lvl1":"API Reference","lvl2":"Other Events","lvl3":""}},
 {"objectID":"7ff1b31f163c4928ce88a79da3c279d1c1c6351ccf3cc5ad2464d2a03174f308","title":"Related Features","url":"/docs/sdk/api-reference#related-features","content":"Human-in-the-Loop (HITL) - Mark tools with requiresConfirmation: true\nGuardrails Middleware - Set middleware per call, in new NeuroLink({ middleware }) or with configureGlobalMiddleware(); add badWords or modelFilter to filter\nConversation History - Use getConversationHistory() method\nMultimodal Chat - Use images array in generate() options\nAuto Evaluation - Enable with enableEvaluation: true\nCLI Loop Sessions - Interactive mode with persistent state\nProvider Orchestration - Set enableOrchestration: true\nRegional Streaming - Use region parameter in generate()\nOffice Documents - Use the files array (or --file) for DOCX, PPTX, XLSX\nPDF Support - Use pdfFiles array for PDF documents\nCSV Support - Use csvFiles array for spreadsheet data\nCLI Commands Reference - CLI equivalents for all SDK methods\nConfiguration Guide - Environment variables and config files\nTroubleshooting - Common SDK issues and solutions\n\nBack to Main README | Next: Visual Demos","hierarchy":{"lvl0":"Sdk","lvl1":"API Reference","lvl2":"Related Features","lvl3":""}},
 {"objectID":"72ff7213f71cd3e590c196c5a1a39a7ab2af152776936e1a647f228cae34de6e","title":"🔧 SDK Custom Tools Guide","url":"/docs/sdk/custom-tools-guide","content":"🔧 SDK Custom Tools Guide\n\nBuild powerful AI applications by extending NeuroLink with your own custom tools.\n\n📋 Overview\n\nNeuroLink's SDK allows you to register custom tools programmatically, giving your AI assistants access to any functionality you need. All registered tools work seamlessly with the built-in tool system across all supported providers.\n\nKey Features\n✅ Type-Safe: Full TypeScript support with Zod schema validation\n✅ Provider Agnostic: Works with all providers that support tools\n✅ Easy Integration: Simple API for tool registration\n✅ Async Support: All tools run asynchronously\n✅ Error Handling: Graceful error handling built-in\n\n🚀 Quick Start\n\nBasic Tool Registration\n\n⚠️ Common Mistakes\n\n❌ Using schema instead of parameters\n\n❌ Using plain JSON schema as parameters\n\n✅ Correct Zod Schema Format\n\n📖 SimpleTool Interface\n\nAll custom tools implement the SimpleTool interface:\n\nInterface Components\ndescription: Clear, actionable description that helps the AI understand when to use the tool\nparameters: Optional Zod schema for validating inputs (highly recommended)\nexecute: Async function that implements the tool's logic\n\n🛠️ Registration Methods\n\nRegister Single Tool\n\nRegister Multiple Tools\n\nGet Custom Tools\n\n💡 Common Use Cases\nAPI Integration\nDatabase Operations\nData Processing\nFile Operations\nExternal Service Integration\n\n🎯 Best Practices\nClear Descriptions\n\nMake tool descriptions specific and actionable:\nParameter Validation\n\nAlways use Zod schemas for type safety:\nError Handling\n\nHandle errors gracefully:\n\nA returned error is classified as a failure everywhere the SDK reports one,\nexactly as a thrown error is. A result is error-shaped when it carries\nisError: true (the MCP convention), a non-null error field ({ error:\n\"User not found\" }), or a status of \"error\" / \"failed\" / \"failure\" /\n\"fail\". Such a call emits tool:end with success: false and the error\ntext, is stored in session memory as success: false, replays on later turns\nas [called <tool> → error], and is reported with isError: true in\nresult.toolExecutions. The model still receives the full object you\nreturned — classification only affects telemetry and memory, never what the\nmodel sees.\nAsync Operations\n\nAll execute functions must return promises:\nTool Naming\n\nUse clear, consistent naming:\n\n🧪 Testing Your Tools\n\nUnit Testing\n\nIntegration Testing\n\n🔍 Debugging Tools\n\nEnable Debug Mode\n\nLog Tool Execution\n\n🚀 Advanced Patterns\n\nTool Composition\n\nTool Middleware\n\nDynamic Tool Registration\n\nForcing a Tool Call\n\ntoolChoice tells the model whether it must call a tool on a step:\n\n| Value                             | Effect                                           |\n| --------------------------------- | ------------------------------------------------ |\n| \"auto\" (default)                | The model decides whether and which tool to call |\n| \"none\"                          | No tool calls on any step                        |\n| \"required\"                      | The model must call at least one tool            |\n| { type: \"tool\", toolName: \"x\" } | The model must call the named tool               |\n\nA forced choice (\"required\" or a named tool) is applied only to the first\ntoolChoiceSteps steps of the tool loop — default 1 — after which the\nmodel is free to answer. Holding a forced choice on every step would compel\na tool call on every step, and the turn could only end when maxSteps ran\nout. \"auto\" and \"none\" are applied unchanged on every step.\n\nFor anything finer, prepareStep runs before every step and may return a\ntoolChoice for that step, which takes precedence over toolChoiceSteps:\n\nprepareStep receives { stepNumber, steps, maxSteps, model }, where steps\nholds one record per completed step (its text, tool calls — with input\nalready parsed into an object — tool results, finish reason and usage,\nincluding prompt-cache tokens where the provider reports them). Only the\nreturned toolChoice is honoured; the legacy model and\nexperimental_activeTools / activeTools fields are accepted for source\ncompatibility but ignored, and their presence is logged once as a warning —\nuse toolFilter / excludeTools to scope tools. A hook that throws is\nlogged and that step falls back to the toolChoice / toolChoiceSteps rule;\na hook still pending when the turn is aborted or times out is released with\nthe abort. Both toolChoice and prepareStep apply to stream() as well.\n\nVertex, Google AI Studio and Bedrock do not honour toolChoice at all today.\nSageMaker honours tools, toolChoice and prepareStep on generate()\nonly: its stream() sends the prompt without tools.\n\n📊 Performance Considerations\nTimeout Handling\nCaching\nBatch Operations\n\n🔒 Security Considerations\n\nInput Sanitization\n\nPermission Checking\n\nRate Limiting\n\n🎉 Complete Example\n\nHere's a complete example combining multiple concepts:\n\n🌐 MCP Server Integration\n\nBeyond simple tool registration, NeuroLink SDK supports adding complete MCP (Model Context Protocol) servers for more complex tool ecosystems.\n\nAdding I","hierarchy":{"lvl0":"Sdk","lvl1":"🔧 SDK Custom Tools Guide","lvl2":"","lvl3":""}},

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@juspay/neurolink",
-  "version": "13.8.15",
+  "version": "13.8.16",
   "packageManager": "pnpm@10.28.2",
   "description": "The pipe layer of an AI nervous system: one interface connecting provider neurons to your application, across three inference types — generate, stream and decide. `decide` returns typed, calibrated judgements from a non-generative model (~400ms, ~$0.00002/call) for routing, tool selection and context budgeting. MCP-native (4 transports), voice TTS/STT/realtime, RAG, agents, memory, compaction, 9 observability exporters. OpenAI · Anthropic · Gemini · Bedrock · Azure · Ollama · TypeSafe Jev and more.",
   "author": {