Changelog

You can now send a node summary of up to 5,000 characters to graph.node.update. Before, the limit was 500 characters, and you could not write back a summary that Zep generated.

An account can now have more than one Account Owner. When an Account Owner gives the Account Owner role to a member, the current Account Owners keep their role. You cannot remove the last Account Owner of an account.

The dashboard now shows credit usage to all Zep Cloud accounts. The Billing page in the EU region also shows credit usage.

During an Enterprise trial, you can now select a self-serve plan on the Billing page of the dashboard.

Auto search now uses the reranker when a search has more than 128 candidates. The reranker scores up to 200 candidates. Before, such a search used reciprocal rank fusion (RRF) order and did not use the reranker.

A guide to build an agent that uses Zep through tools was added in the Build an Agent with Zep section.

Each call to the deprecated graph.add_batch and thread.add_messages_batch methods now creates a Batch API batch. The batch shows in batch.list and in the dashboard. Zep sends the ingest.batch.completed webhook for these batches on the same batch outcomes as other Batch API batches. The task status that the call returns follows the batch status.

The minimum interval between two summary updates for one entity is now 15 minutes. Before, the interval was 30 minutes.

In the dashboard graph visualization, each edge label now has an opaque background with a border in the edge color. The labels are clear in dark mode and in light mode. A label longer than 32 characters is shortened.

This change applies to a graph with more than 1,000 episodes. When Zep extracts facts from a new episode, Zep now uses the most recent episodes as context. Before, Zep could use older episodes as context.

Each custom edge type can now have up to 100 source-target pairs. The previous limit was 10.

Two facts in a batch can have the same edge type and connect the same entities in the opposite order. Batch ingestion now detects these facts as duplicates. Before, both facts could stay in the graph.

The user list and the graph list in the dashboard now show the UUID of each user and graph. Click a row to open the detail page. A user or graph that has no developer-assigned ID now opens and works on its detail page.

The dashboard has a new visual design. The dashboard copy now uses the word context in place of memory on these pages:

• The sign-in page
• The onboarding wizard
• The dashboard tour
• The Playground

A batch can have thread messages with an ignored role between other messages. Zep now uses these skipped messages as context during extraction. Zep reads the messages in their original order. Before, extraction did not read these messages.

When you create or clone a user, the user_id cannot equal the UUID of an existing user in the project. The API returns a 400 error for this request.

Every webhook payload that identifies a graph now includes graph_uuid. A payload for a user graph also includes user_uuid. The existing payload fields do not change.

The Account > Members page in the dashboard now shows an added or removed member immediately. Before, the change appeared only after you reloaded the page.

Zep now deletes free-plan accounts that have no API or dashboard activity for 90 days. The Account Owner receives warning emails before the deletion, starting after 60 days of inactivity. The deletion applies only to free-plan accounts that are hosted in the Zep Cloud US region. Accounts in other Zep Cloud regions, paid accounts, enterprise accounts, and BYOC accounts are not affected.

The SDK reference descriptions of the deprecated graph.episode.get_nodes_and_edges and graph.node.get_edges methods now name the replacement SDK methods.