Memory in CrewAI

Memory in CrewAI enables agents to retain past interactions, outputs and contextual information ensuring that tasks are carried out in a coherent and structured manner. In multi-agent workflows, agents must often build on previous work. Without memory, each agent would begin from scratch and lose context.

Working of Memory in CrewAI

When the memory parameter is set to True for an agent or a crew, it enables short-term, long-term and entity memory. Together, these components ensure that agents can retain context, recall past work and build structured knowledge.

• Short-Term Memory: Uses ChromaDB with retrieval-augmented generation (RAG) to provide the current session’s context.
• Long-Term Memory: Uses SQLite3 to store task results and knowledge across sessions.
• Entity Memory: Uses RAG to capture and recall details about entities such as people, places and concepts.
• Storage Location: Stored in a platform-specific directory determined by the app dirs package.
• Custom Storage Directory: Can be set by defining the CREWAI_STORAGE_DIR environment variable.

Implementation of memory in CrewAI

We will be implementing memory in CrewAI by enabling it for agents and inspecting how it stores and retrieves information across tasks and sessions.

1. Defining Agents with Memory

We define three agents: a Writer, an Editor and a Publisher. The Writer has memory enabled to recall ideas and context while producing the manuscript.

• role: The agent’s function in the workflow.
• goal: The objective the agent aims to achieve.
• backstory: Background information influencing agent behavior.
• verbose: When set to True, provides detailed output during execution.
• memory: Enables or disables memory for the agent.

2. Defining Tasks

Each task specifies a description, an agent responsible for execution and expected output. Tasks can also depend on the results of previous tasks.

• description: Explains what the task should accomplish.
• agent: The agent responsible for completing the task.
• expected_output: The expected result of the task.
• context: Specifies dependencies by passing outputs of earlier tasks.

3. Creating the Crew

The agents and tasks are grouped into a Crew. We specify a sequential process, meaning each task runs in order.

• agents: List of agents participating in the crew.
• tasks: List of tasks executed by the crew.
• process: Defines the execution order (Process.sequential ensures tasks run in sequence).
• verbose: Enables detailed logging.
• kickoff(): starts the crew’s execution.

Output:

if memory=True was not enabled, the Editor would not automatically recall the Writer’s manuscript and would start editing without any context. With memory enabled, the Editor receives the Writer’s output as part of its context, leading to meaningful edits instead of disconnected results.

4. Checking Memory Storage

CrewAI stores memory locally. The following code retrieves the storage path and lists stored files.

• db_storage_path(): Returns the base directory where CrewAI stores memory.
• os.listdir(): Lists files and subdirectories.
• os.path.isdir(): Identifies directories within the storage path.

Output:

CrewAI storage location: /root/.local/share/content

Stored files and directories:
latest_kickoff_task_outputs.db