Skip to main content
Lyzr agents can remember across turns in a session and across sessions entirely. This page explains the memory model and when to use each type.

​
Session memory (short-term)

By default, agents have no memory between messages; each message is independent. Enabling memory gives agents access to conversation history. Lyzr uses a hybrid short-term / long-term model:
  • The most recent N messages are stored word-for-word (short-term).
  • Older messages are summarized and retained as context (long-term).
The default is 10 messages stored as short-term. Messages beyond that are summarized. Adjust this with the memory slider in agent configuration. This prevents context overload. A conversation history of 50 raw messages would increase latency and hallucination risk. Summarization keeps context manageable while preserving meaning.

​
Memory providers

Cognis is a production-grade memory module that requires zero configuration. Cognis automatically stores interactions, retrieves relevant context, updates stale memories, and handles temporal reasoning, including understanding that “last week” is different from “last year.” Cognis also supports cross-session memory: the agent remembers past conversations with the same user across multiple sessions. Enable this with the Cross-session memory toggle in agent configuration. Cognis is also available as a standalone service (Lyzr Blocks) and integrates with external tools via MCP, including Cursor, Claude, Zed, and custom agents.

​
Lyzr Memory (legacy)

Lyzr Memory is the predecessor to Cognis. It is still supported and offers configurable short-term / long-term window controls via a manual slider. Use Cognis for new agents.

​
Amazon Bedrock AgentCore Memory

Amazon Bedrock AgentCore Memory is a fully managed AWS service for agents that need native AWS integration. It requires you to bring your own AWS credentials (BYOK).

​
Global Context

Global Context is org-level context that applies to every agent in your workspace without per-agent configuration. Use it to inject:
  • Company tone and brand voice
  • Product descriptions and terminology
  • Compliance rules that apply to all agents
  • Shared reference information
You update Global Context once, and all agents automatically use the new version.

​
Memory vs. Knowledge Base

MemoryKnowledge Base
What it storesConversation historyDocuments, websites, structured data
Updated byConversationsManual upload or scheduled sync
Retrieved bySession ID or user IDSemantic search query
Use casePersonalizing responses, maintaining continuityGrounding answers in source material
Use both together for best results: memory for who the user is and what they’ve asked before, Knowledge Base for what your organization knows.

​
Next steps