@stratusagent/memory-sqlite

Agent memory on one SQLite file, as a plugin. It registers a memory store named sqlite through the plugin seam (19); a trusted config selects it for the fleet, and every agent's memory.remember, memory.recall, memory.forget, and memory.pin — and the memory each turn's prompt is built from — go through it instead of the built-in file store.

Install and enable

npm install @stratusagent/memory-sqlite

// ~/.stratus/config.json — a trusted config only
{
  "plugins": {
    "@stratusagent/memory-sqlite": { "enabled": true, "path": "~/.stratus/memory.sqlite" }
  },
  "memoryStore": "sqlite"
}

path is required: where the database lives is your decision, not one the plugin guesses inside a directory it does not own. ~ expands as in a shell. The file and its WAL sidecars are owner-only (0600), like the file store and the session database.

What it is, and is not

The same memory contract as the built-in store — per-agent keying, search as whole-token AND matching over content and about keys, newest first with ties broken by id, bounded reads by count and bytes, tombstones rather than deletes, supersession scoped to the successor's validity window, a pinned core that refuses rather than evicting, the topic index, an operator audit read, trust re-assertion — on a different shape: rows in SQLite, no derived index. Every read selects an agent's live rows and applies the contract's own rules from @stratusagent/core, so this store and the file store cannot disagree about what a query matches or which entries a bounded read keeps.

Two tables hold what the file store keeps in its record lane and its index: pins, ordered by arrival rather than by timestamp, so a budget is allocated the way O_APPEND allocates it there; and usage, the recall counters, which are derived and are the only thing here a rebuild could not restore — dropping that table loses statistics, never memories.

It exists to prove that AgentMemoryStore holds for a shape that is not JSONL-plus-FTS5, and it is a real store; it is not a faster one. Selecting it moves new memories here — nothing is migrated from the file store, and switching back leaves what was written here where it is.