Chat message history stores a history of the message interactions in a chat.
Class hierarchy:
.. code-block::
BaseChatMessageHistory --> <name>ChatMessageHistory # Examples: FileChatMessageHistory, PostgresChatMessageHistory
Main helpers:
.. code-block::
AIMessage, HumanMessage, BaseMessage
Chat message history that is backed by Cassandra.
Chat message history backed by Azure CosmosDB.
Chat message history that stores history in AWS DynamoDB.
This class expects that a DynamoDB table exists with name table_name
Chat message history that stores history in a local file.
Chat message history backed by Google Firestore.
Chat message history stored in Kafka.
Chat message history cache that uses Momento as a backend.
Chat message history stored in a Redis database.
Uses Rockset to store chat messages.
To use, ensure that the rockset python package installed.
Chat message history stored in an SQL database.
Chat message history that stores messages in Streamlit session state.
Represents a chat message history stored in a TiDB database.
Chat message history stored in an Upstash Redis database.
Chat message history stored in a Xata database.
Chat message history that uses Zep as a backend.
Recommended usage::
# Set up Zep Chat History
zep_chat_history = ZepChatMessageHistory(
session_id=session_id,
url=ZEP_API_URL,
api_key=<your_api_key>,
)
# Use a standard ConversationBufferMemory to encapsulate the Zep chat history
memory = ConversationBufferMemory(
memory_key="chat_history", chat_memory=zep_chat_history
)
Zep provides long-term conversation storage for LLM apps. The server stores, summarizes, embeds, indexes, and enriches conversational AI chat histories, and exposes them via simple, low-latency APIs.
For server installation instructions and more, see: https://docs.getzep.com/deployment/quickstart/
This class is a thin wrapper around the zep-python package. Additional
Zep functionality is exposed via the zep_summary and zep_messages
properties.
For more information on the zep-python package, see: https://github.com/getzep/zep-python
Chat message history that uses Zep Cloud as a backend.
Recommended usage::
# Set up Zep Chat History
zep_chat_history = ZepChatMessageHistory(
session_id=session_id,
api_key=<your_api_key>,
)
# Use a standard ConversationBufferMemory to encapsulate the Zep chat history
memory = ConversationBufferMemory(
memory_key="chat_history", chat_memory=zep_chat_history
)
Zep - Recall, understand, and extract data from chat histories. Power personalized AI experiences.
Zep is a long-term memory service for AI Assistant apps. With Zep, you can provide AI assistants with the ability to recall past conversations, no matter how distant, while also reducing hallucinations, latency, and cost.
see Zep Cloud Docs: https://help.getzep.com
This class is a thin wrapper around the zep-python package. Additional
Zep functionality is exposed via the zep_summary, zep_messages and zep_facts
properties.
For more information on the zep-python package, see: https://github.com/getzep/zep-python
Chat message history that stores history in Elasticsearch.
Chat message history stored in a Postgres database.
DEPRECATED: This class is deprecated and will be removed in a future version.
Use the PostgresChatMessageHistory implementation in langchain_postgres.
Chat message history stored in a SingleStoreDB database.
Firestore Chat Message History.
Cassandra-based chat message history, based on cassIO.
Kafka-based chat message history by using confluent-kafka-python. confluent-kafka-python is under Apache 2.0 license. https://github.com/confluentinc/confluent-kafka-python
Azure CosmosDB Memory History.