​
Understanding Digital Twin Memory Systems

Your digital twin uses two complementary memory systems to provide both immediate context and long-term personalization. Understanding the difference helps you optimize your interactions.

​
Two Types of Memory

Your digital twin operates with dual memory systems that work together to enhance your experience:

Conversation History

Short-term conversation context for immediate continuity

User Memory

Long-term storage for persistent personalization

​
Conversation History (Short-Term Context)

Think of this as your digital twin’s “working memory” for the current conversation.

​
Key Characteristics

  • Temporary: Only remembers recent conversations (configurable: 1-25 dialogues)
  • Session-focused: Provides context for ongoing discussions
  • Adjustable: Change in Settings → Remember History (bottom-left)
  • Cost-aware: More history = higher token usage and processing costs
  • Context window: Maintains conversation flow and understanding

​
How It Works

Conversation history is injected into each prompt before being sent to the AI model. The system selects only conversations from the current session to maintain logical continuity and prevent context confusion from mixing unrelated conversation threads.

​
Practical Example

You: "Let's work on API documentation for our payment system"
Twin: "Great! I'll help with your payment API docs."

[10 messages later...]

You: "Add the error codes section"
Twin: "I'll add error codes to the payment API documentation we've been building."
The digital twin remembers you’re working on payment API docs because it’s within the history window.

​
Benefits & Trade-offs

  • Higher values (8-15): Better context for complex, multi-step conversations but higher costs
  • Lower values (1-5): More cost-effective for simple queries but limited context
  • Optimal balance: Adjust based on conversation complexity and cost preferences
Learn more at Conversation History: How it works

​
User Memory (Long-Term Personalization)

Follows you across multiple digital twins and conversations. User memory collects information about you and your interactions to personalize your experience and enhance your overall AI interactions.

​
Key Characteristics

  • Permanent: Stored long-term across all conversations and sessions
  • Cross-session: Available weeks or months later across different digital twins
  • Selective: Only stores important, relevant information automatically
  • Secure: Private to your account and fully protected
  • Automatic: Digital twin intelligently decides what’s important to remember
  • Structured: Organized by namespaces (personal, preferences, work, etc.)

​
What Gets Stored

  • Personal details: Role, company, location, important dates
  • Preferences: Communication style, response format, technical level
  • Decisions: Important choices made during conversations
  • Context: Ongoing projects, goals, and key information
  • Learning: Feedback and corrections you provide

​
Practical Example

Session 1: "I'm a technical writer at Acme Corp, and I prefer concise documentation"
[User Memory stores: Role=Technical Writer, Company=Acme Corp, Style=Concise]

Session 2 (weeks later): "Help me with new API docs"
Twin: "I'll create concise API documentation for Acme Corp, matching your preferred style."

Session 3 (different twin): "Review this code"
Twin: "As a technical writer at Acme Corp, I'll focus on documentation clarity and conciseness."

​
Benefits

  • Consistency: Same personalized experience across all interactions
  • Efficiency: No need to repeat preferences or context
  • Intelligence: Builds understanding of your needs over time
  • Continuity: Maintains context even after long breaks
  • Cross-platform: Works across different digital twins and assistants
Learn more at User Memory: How it works

​
Memory Systems Working Together

The two memory systems complement each other perfectly:
  • Conversation History handles immediate context and ongoing discussions
  • User Memory provides persistent personalization and long-term context
  • Together, they create a seamless, intelligent experience that feels natural and personalized

​
Best Practices

  1. Adjust history length based on conversation complexity
  2. Trust automatic memory storage - your twin knows what’s important
  3. Provide feedback to improve long-term personalization
  4. Use clear preferences early in relationships with new twins

​
User Memory vs Conversation History

Don’t confuse User Memory with Conversation History! They serve different but complementary purposes.
Conversation History is temporarily injected into each prompt and contains the recent dialogue exchanges (configurable 1-25 messages). While essential for maintaining context within a conversation, excessive history consumes unnecessary credits and varies between different conversations or assistants. It’s best used for immediate context like “continue the code from my last message” or “refine that previous suggestion.” User Memory, however, is your persistent preference vault accessible across all conversations and Digital Twins through agent tools. It stores lasting preferences like your technical interests, learning style (reading/writing), communication preferences (short responses), and personal details (age 53, lives in Saint-Louis). This memory travels with you whether you’re using the Code Assistant, Conversational Assessment, or any other specialized assistant, ensuring consistent personalization without repeatedly explaining your preferences.
Understanding the distinction between these two memory systems is crucial for optimizing your AI experience.
AspectUser MemoryConversation History
DurationPermanent (weeks/months/years)Temporary (current conversation)
ScopeImportant personal data & preferencesRecent dialogue exchanges
PurposeLong-term personalizationConversation continuity
StorageSelective key informationFull conversation context
ControlAutomatic + manual managementUser adjustable (1-15 dialogues)
ContentPreferences, goals, decisionsComplete message exchanges
Cost ImpactMinimal (structured parameters)Direct (more history = more tokens)
AccessibilityCross-platform, all assistantsSession-specific only
OrganizationNamespaced and categorizedSequential chronological order
OptimizationOrganize with namespaces and periodic cleanupAdjust length based on complexity

​
When to Use Each System

Use Conversation History for:
  • Referencing previous messages in the current discussion
  • Building complex arguments or explanations over multiple turns
  • Maintaining context for ongoing tasks or projects within a session
  • Following up on specific points made earlier in the conversation
Use User Memory for:
  • Storing permanent preferences and personal information
  • Maintaining consistency across different conversations and assistants
  • Avoiding repetitive explanations of your role, company, or preferences
  • Building long-term personalization that improves over time

​
Bottom Line

Conversation History = temporary context for current chat; User Memory = permanent preferences that follow you everywhere!