A failed batch item no longer stops the rest of the batch
A batch that hit an item Zep could not ingest abandoned the items behind it.
Processing now continues past a failed item, retries only the part that failed,
and keeps the results already produced. batch.list_items reports an error for
each item that did not ingest.
Large batches start processing without timing out
batch.process now returns as soon as the batch is queued and prepares the
batch in the background. Processing a large draft previously ran past the
request timeout and left the batch unstarted.
Batch usage is counted when processing starts
Batch items are counted against your episode usage when you call
batch.process, not when you add them, so a draft you delete without
processing is no longer billed. Each item is counted on its own, matching
graph.add, so a batch of many short items consumes more than it did before.
Policy-based access control for Memory MCP standalone graphs
Enterprise accounts on Zep managed cloud can now move a Memory MCP connection from project-wide standalone graph access to UserGroup access control, where a user reaches a standalone graph only through an enforced policy grant. The move is one-way; open Settings ▸ MCP to review and enable it.
Zep Memory plugin documentation for Claude Code and Codex
Instructions for installing the Zep Memory plugin in Claude Code and Codex were added to Use Zep in Claude / ChatGPT / Cursor.