Threads

Overview

Threads represent a conversation. Each User can have multiple threads, and each thread is a sequence of chat messages.

Chat messages are added to threads using thread.add_messages, which both adds those messages to the thread history and ingests those messages into the user-level knowledge graph. The user knowledge graph contains data from all of that user’s threads to create an integrated understanding of the user.

Adding a Thread

threadIds are arbitrary identifiers that you can map to relevant business objects in your app, such as users or a conversation a user might have with your app. Before you create a thread, make sure you have created a user first. Then create a thread with:

1
client = Zep(
2
    api_key=API_KEY,
3
)
4
thread_id = uuid.uuid4().hex # A new thread identifier
5
6
client.thread.create(
7
    thread_id=thread_id,
8
    user_id=user_id,
9
)

Getting Messages of a Thread

1
messages = client.thread.get(thread_id)

Deleting a Thread

Deleting a thread deletes it and its associated messages. It does not however delete the associated data in the user’s knowledge graph. To remove data from the graph, see deleting data from the graph.

1
client.thread.delete(thread_id)

Listing Threads

You can list all Threads in the Zep Memory Store with page_size and page_number parameters for pagination.

1
# List the first 10 Threads
2
result = client.thread.list_all(page_size=10, page_number=1)
3
for thread in result.threads:
4
    print(thread)

Automatic Cache Warming

When you create a new thread, Zep automatically warms the cache for that user’s graph data in the background. This optimization improves query latency for graph operations on newly created threads by pre-loading the user’s data into the hot cache tier.

The warming operation runs asynchronously and does not block the thread creation response. No additional action is required on your part—this happens automatically whenever you create a thread for a user with an existing graph.

For more information about Zep’s multi-tier caching architecture and manual cache warming, see Warming the User Cache.