Skip to navigation

Some features listed below may be pending rollout and not immediately available yet.

SCIM provisioning (beta)

You can now provision account Members and Groups in Zep from an identity provider (IdP) with SCIM. You can map each IdP Group to a Zep role. SCIM provisioning is in beta and requires the Enterprise plan. Zep turns on SCIM for each Enterprise account on request.

Read the docs
dashboardsecuritygraphsdkbreaking-change

Reserved connector metadata key

The connector key is now reserved in episode metadata and message metadata. A request that adds or updates episode metadata or message metadata with the connector key returns HTTP 400, also when the value is null. User metadata and batch-level metadata can still use the key.

Read the docs
dashboardsecuritygraphsdkbreaking-change

Content policies require the Enterprise plan

Content policies now require the Enterprise plan. Zep also turns on content policies for each Enterprise account on request. An account without these two conditions cannot write a content policy with rules or create a protected graph. The API returns HTTP 403 with content_policy_not_entitled. Zep ingests new episodes of an existing protected graph on such an account without evaluation.

graphsdksecuritybug-fixdocs

Fact timestamps documentation

Documentation about how the episode reference time sets fact timestamps was added to the Facts page.

Read the docs
graphsdksecuritybug-fixdocs

Custom edge attributes without a copy of the fact

Zep now sets a custom edge attribute to null when the fact does not state the data that the attribute describes. Before, extraction could copy the fact text into the attribute.

Read the docs
graphsdksecuritybug-fixdocs

User node of a graph clone for a target user

The v3 graph.clone method can clone a user graph for a target user with target_user_id. The user node of the clone now has the name embedding of the target user. Before, the user node kept the name embedding of the source user. A node search for the name of the target user could then miss the user node.

graphsdksecuritybug-fixdocs

User node update from the v4 API

When you change the first_name, last_name, or email of a user with the v4 user.update method, Zep now updates the user node in the user graph. Before, the user node kept the old name and attributes.

Read the docs
graphsdkbug-fixdocs

Source episodes of nodes and edges

Node and edge responses now list only the source episodes of the node or the edge. Before, the episode lists could contain internal episodes that Zep creates when you add a node, a fact triple, or a hyperedge directly. For an edge, the change applies to episode_uuids in v4 and to episodes in v3.

Read the docs
graphsdkbug-fixdocs

Ontology design best practices

Ontology design best practices were added to the Customizing graph structure page.

Read the docs
graphsdkbug-fixdocs

Webhooks for plans that include webhooks

Zep now sends episode and batch webhooks only for an account whose plan includes webhooks. An account without webhooks on its plan can still disable webhooks and open the webhook portal.

Read the docs
graphsdkdashboardbug-fix

Invalidation of a fact that a later fact ends

When a new fact states that an earlier fact ended, Zep now invalidates the earlier fact. The invalid_at value of the earlier fact is the end date of the new fact. When the new fact has no date, Zep uses the reference time of its episode. Before, the earlier fact stayed valid unless the new fact had a later start date.

Read the docs
graphsdkdashboardbug-fix

Node search from BFS origin nodes

Node search with bfs_origin_node_uuids now returns the entity nodes that the search reaches through observation nodes. Before, observation nodes counted against the node limit of the traversal. The search could then return few or no entity nodes.

Read the docs
graphsdkdashboardbug-fix

v4 actions in the API logs

The API Logs page of the dashboard now shows the action of each v4 API request. You can filter the logs by a v4 action. To open the page, go to Account > API Logs.

graphsdkdashboardbug-fix

Extraction of named entities in longer entity names

When an entity name contains a different named entity, Zep now also extracts the named entity as a separate entity. For example, the text “Acme Cloud billing outage” now gives the entity “Acme Cloud” and the entity “Acme Cloud billing outage”. A fact can then connect the two entities. Zep does not split a proper name that identifies one entity, such as “Bank of America”.

graph

Agent Skills search with a long query

The agent.skill.search method now accepts a query that has more than 64 terms. Search uses the first 64 terms of the query and ignores the other terms. Before, a query with more than 64 terms returned an HTTP 400 error. The maximum query length of 512 bytes does not change.

Read the docs
sdkbug-fixdocs

Edge type hierarchies (closed beta)

You can now group custom edge types into types and subtypes with the optional edge_type_hierarchy field on project.set_ontology and graph.set_ontology. Zep classifies each extracted edge into the deepest subtype that applies. A search filter on an edge type also matches its subtypes. This feature is in closed beta and is available only for select accounts.

graphsdkdashboardsecuritybug-fix

Graph Assistant opt-in for HIPAA accounts

The Graph Assistant is now off for a HIPAA account until the account opts in. To opt in, an account owner or admin turns on Graph Assistant on the Account Settings page of the dashboard. Before the opt-in, the assistant sidebar shows a message that tells you how to opt in.

Read the docs
graphsdkdashboardsecuritybug-fix

Observation updates for graphs with an empty observation name

Zep now continues to update the observations of a graph when the model returns an observation with an empty name. Before, this answer stopped all observation updates for that graph.

Read the docs
graphsdkdashboardsecuritybug-fix

User node name for a user with no user ID

When a user has no user ID, the user node in the user graph now uses the user UUID as its identifier. Before, the user node summary showed an empty identifier.

graphbug-fixdocsbatch

GPT-5.4 Mini and GPT-5.4 Nano removed from BYOM

You can no longer select GPT-5.4 Mini or GPT-5.4 Nano as the model of a BYOM configuration. The change applies to the OpenAI provider and to the Azure OpenAI provider. Select GPT-6 Luna or GPT-5.6 Luna in place of these models.

Read the docs
graphbug-fixdocsbatch