eve Integration

​

Overview

1. Recall. Before every turn, it runs one search (dumb_search) for the user’s message. The matches go into the model’s context as data, not instructions. This makes no inference calls.
2. Tools. The model gets <slot>__search, which looks further back, and <slot>__remember, which saves one note.
3. No automatic capture. Turns are never saved on their own. See Why there is no automatic capture.

​

One-click template

​

iMessage

npx eve add channel/linq     # or: npx eve add channel/photon

​

Add claude-mem to an existing eve agent

npm install claude-mem

import { claudeMem } from "claude-mem/eve";
import { defineMemory } from "eve/memory";
import { byPrincipal } from "eve/memory/scope";

export default defineMemory({
  description: "Recall and save durable context for the current user.",
  provider: claudeMem({ apiKey: process.env.CLAUDE_MEM_API_KEY }),
  scope: byPrincipal,
});

​

Options

​

Security

• The key owns the memory. A cmem.ai key reads and writes one person’s memory. The default configuration keeps each eve scope in its own project, and every search filters on that project on the server.
• Only use searchAllProjects for a single-owner agent. With it on, anyone the slot’s scope admits can read the key owner’s whole memory. Make scope return null for everyone else, the way the template does.
• Tools are bound to the scope. The model cannot point search or remember at another project.
• Recalled text is data. It arrives inside <claude_mem_recall> with markup escaped, and is placed as a user message, never as system instructions.
• Saving needs write access. A Pro key from cmem.ai/pro/key can read and write. A read-only key still recalls and searches, and remember reports that saving is not allowed. On the server, cmem.ai drops <private> regions and redacts secrets from saved notes.
• Failures are visible. If cmem.ai can’t be reached, the turn still runs. The provider logs [claude-mem/eve] recall failed and tells the model memory was unavailable. A cancelled turn is not reported as a memory failure.

​

Why there is no automatic capture