Some features listed below may be pending rollout and not immediately available yet.
The graph visualizer assistant resolves follow-up questions
A follow-up question that referred to an earlier answer, such as “when did she move there?”, was searched as written and often returned results that did not match the conversation. The assistant now rewrites a follow-up question into a standalone question before it searches the graph. The panel shows this rewrite as the first step of the turn.
BYOM webhooks name the provider that rejected your credential
A byom.request_failed webhook event reported the primary provider and model
for every failure, also when the fallback provider ran. The event now names the
provider and model that produced the failure, and a rejected credential now
reports BYOM_CREDENTIALS_INVALID. Ingestion no longer retries a request that
a provider rejected because of the credential, so the failure reaches you on the
first attempt.
Batched thread messages ingest with the thread user
A thread message ingested through the Batch API did not carry the speaker and
the user identity that thread.add_messages adds during extraction, so the
same conversation produced a different graph. Both paths now produce the same
graph. Reads return the content you sent, and usage is metered on that content.
Connect Gemini Enterprise to the MCP server
Enterprise accounts can create pre-registered OAuth clients for Gemini Enterprise from the MCP Server page. The page shows the client secret once and lists and deletes existing clients. Listing and deletion stay available on every plan.
Ask questions about a graph in the visualizer
The graph visualizer in the dashboard has an assistant that answers read-only questions about the graph you are viewing. It shows each retrieval step and cites the facts and entities behind the answer. The assistant is in limited rollout, so Ask graph is shown only when it is enabled for your account.
Thread message metadata is episode metadata
Metadata on a thread message now behaves the same as metadata added through
graph.add. Zep projects it onto the facts, entities, and summaries derived
from the message, graph search filters on it, and source-based access control
evaluates it. Message metadata accepts at most 10 keys with scalar or
array-of-scalar values. On an update, a key set to null is removed.
Self-referencing facts are kept
Extraction dropped a fact whose source and target are the same entity, which lost personal states and routines. Those facts are now kept in the graph.
The dashboard returns you to the project you were viewing
Opening an account page and then returning to your projects opened the first project in your list, not the project you were working in. The dashboard now remembers the project you viewed last and returns you to it. It falls back to the first project you can access when that project is gone.