Memory

Bitca provides 3 types of memories for building a great Agent experience (AX):

  1. Chat History: previous messages from the conversation, we recommend sending the last 3-5 messages to the model.

  2. User Memories: notes and insights about the user, this helps the model personalize the response to the user.

  3. Summaries: a summary of the conversation, which is added to the prompt when chat history gets too long.

Before we dive in, let’s understand the terminology:

  • Session: Each conversation with an Agent is called a session. Sessions are identified by a session_id.

  • Run: Every interaction (i.e. chat) within a session is called a run. Runs are identified by a run_id.

  • Messages: are the individual messages sent to and received from the model. They have a role (system, user or assistant) and content.

Built-in Memory

Every Agent comes with built-in memory that can be used to access the historical runs and messages. Access it using agent.memory

runslist[AgentRun]

The list of runs between the user and agent. Each run contains the input message and output response.

messageslist[Message]

The full list of messages sent to the model, including system prompt, tool calls etc.

Example

agent_memory.py

from bitca.agent import Agent
from bitca.model.openai import OpenAIChat
from rich.pretty import pprint


agent = Agent(
    model=OpenAIChat(id="gpt-4o"),
    # Set add_history_to_messages=true to add the previous chat history to the messages sent to the Model.
    add_history_to_messages=True,
    # Number of historical responses to add to the messages.
    num_history_responses=3,
    description="You are a helpful assistant that always responds in a polite, upbeat and positive manner.",
)

# -*- Create a run
agent.print_response("Share a 2 sentence horror story", stream=True)
# -*- Print the messages in the memory
pprint([m.model_dump(include={"role", "content"}) for m in agent.memory.messages])

# -*- Ask a follow up question that continues the conversation
agent.print_response("What was my first message?", stream=True)
# -*- Print the messages in the memory
pprint([m.model_dump(include={"role", "content"}) for m in agent.memory.messages])

Persistent Memory

The built-in memory only lasts while the session is active. To persist memory across sessions, we can store Agent sessions in a database using AgentStorage.

Storage is a necessary component when building user facing AI products as any production application will require users to be able to “continue” their conversation with the Agent.

Let’s test this out, create a file persistent_memory.py with the following code:

persistent_memory.py

Run the agent

Install dependencies and run the agent:

You can view the agent sessions in the sqlite database and continue any conversation by providing the same session_id.

Read more in the storage section.

User preferences and conversation summaries

Along with storing chat history and run messages, AgentMemory can be extended to automatically classify and store user preferences and conversation summaries.

To do this, add a db to AgentMemory and set create_user_memories=True and create_session_summary=True

User memories are stored in the AgentMemory whereas session summaries are stored in the AgentStorage table with the rest of the session information.

Example

personalized_memories_and_summaries.py

Attributes

Parameter
Type
Default
Description

memory

AgentMemory

AgentMemory()

Agent’s memory object used for storing and retrieving information.

add_history_to_messages

bool

False

If true, adds the chat history to the messages sent to the Model. Also known as add_chat_history_to_messages.

num_history_responses

int

3

Number of historical responses to add to the messages.

create_user_memories

bool

False

If true, create and store personalized memories for the user.

update_user_memories_after_run

bool

True

If true, update memories for the user after each run.

create_session_summary

bool

False

If true, create and store session summaries.

update_session_summary_after_run

bool

True

If true, update session summaries after each run.

Last updated