megachangelog
Feature

Persistent memory for eve agents

Eve agents can now retain context across sessions using persistent memory organized into slots with configurable providers and scopes. Memory is automatically retrieved before each turn and added to the model's context, with support for file storage, Supermemory, Upstash, and custom providers.

agents can now retain context across sessions and use it in future conversations.eve

Persistent is organized into slots. You can define named slots in files under . Each slot specifies a provider, which stores and retrieves the memory, and a scope, which determines who or what shares it. For example, you can keep separate memory for each authenticated user.memoryagent/memory/

Before each turn, eve retrieves relevant memory and adds it to the model's context. Depending on the provider, memory can be updated automatically after a turn, through tools the agent uses, or through both methods.

To add eve's built-in file memory provider, run:

The command creates a memory slot scoped to each authenticated caller:file

For agents deployed on Vercel, file memory uses a private store so saved memories persist across restarts and deployments.Vercel Blob

Other supported memory providers include , , and . You can also connect another storage system or memory service by .SupermemoryUpstash AgentKitKybernesis Arcanabuilding a custom provider

Read the to choose a provider and get started.memory documentation

Read more

agentsmemorycontextstorageai

Source: original entry ↗