Session Persistence

​

When to use this

• Complete Quickstart to understand basic operations
• Ensure you have LLM Providers configured
• Have an existing knowledge graph created with remember()
• Caching must be enabled and at least one session must exist (created by prior cognee.recall() calls with a session_id)

​

Code in Action

import asyncio
import cognee
from cognee import SearchType
from cognee.memify_pipelines.persist_sessions_in_knowledge_graph import (
    persist_sessions_in_knowledge_graph_pipeline,
)
from cognee.modules.users.methods import get_default_user

async def main():
    await cognee.remember(
        "Alice moved to Paris in 2010. She works as a software engineer.",
        dataset_name="session_demo",
        self_improvement=False,
    )

    # Build session history with recall
    await cognee.recall(
        query_type=SearchType.GRAPH_COMPLETION,
        query_text="Where does Alice live?",
        datasets=["session_demo"],
        session_id="demo_session",
    )
    await cognee.recall(
        query_type=SearchType.GRAPH_COMPLETION,
        query_text="What does she do for work?",
        datasets=["session_demo"],
        session_id="demo_session",
    )

    # Persist the session into the graph
    user = await get_default_user()
    await persist_sessions_in_knowledge_graph_pipeline(
        user=user,
        session_ids=["demo_session"],
        dataset="session_demo",
    )

asyncio.run(main())

​

What Just Happened

1. Remember — builds a knowledge graph from your text.
2. Recall with session_id — runs two recalls that accumulate Q&A history in the session cache under "demo_session".
3. get_default_user() — retrieves the authenticated user. This pipeline requires a User object with write access.
4. persist_sessions_in_knowledge_graph_pipeline(user, session_ids, dataset) — reads the cached session data and writes it into the knowledge graph.

​

What Changed in Your Graph

• New nodes are created from the session Q&A history, grouped under the user_sessions_from_cache node set.
• The session data is processed internally into graph memory, so entities and relationships from the session content become part of the graph.
• Persistence is incremental: each run only ingests the Q&A entries added since the last successful persist for that session. Re-running on an unchanged session adds nothing new, so you can safely call it repeatedly as a session grows without re-embedding or duplicating the earlier history.

​

Additional Information

• Runnable session persistence demo available on our GitHub