LaunchKit · 2026
Back to Skills

engram

Persistent semantic memory layer for AI agents.

1
1.5k downloads
by @dannydvm

Setup & Installation

openclaw skills install @dannydvm/engram

Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:

npx clawhub install engram

Version History

v0.2.1Feb 5, 2026 - Version note by skill developer:

Persistent semantic memory with biological decay, typed memories, relationships, and agent scoping. Zero API cost.

What This Skill Does

Engram is a local-first persistent memory layer for AI agents, backed by SQLite and LanceDB with Ollama embeddings. It stores typed memories (facts, decisions, preferences, events, relationships) across sessions and surfaces them via semantic search and context-aware recall. Memory decay, deduplication, agent scoping, and graph relations are built in.

Runs entirely local with no token cost and no cloud dependency, so memory persists through context compaction and session crashes without sending data to an external service.

When to use it

  • Recalling a client's communication preferences from a session three weeks ago
  • Storing a database architecture decision so future agents don't revisit it
  • Ingesting a meeting transcript to automatically extract structured memories
  • Searching past project milestones before drafting a status update
  • Keeping memories isolated per agent so two bots don't share unrelated context

Example Workflow

Here's how your AI assistant might use this skill in practice.

INPUT

User asks: What did we decide about the deployment setup for the new client?

AGENT
  1. 1Run `engram recall "client deployment setup" --limit 10` to surface the most relevant past memories
  2. 2Review returned memories ranked by semantic similarity, recency, and salience
  3. 3Identify the stored decision memory: "Chose Docker Compose over Kubernetes for simplicity on small clients"
  4. 4Check related memories via `engram relations <memory-id>` to find linked facts or follow-up events
  5. 5Return the decision with full context to the user
OUTPUT

"We decided on Docker Compose over Kubernetes for this client (stored 2026-01-15). Related: client prefers minimal ops overhead, deployment target is a single VPS."

Requirements

Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.

Ollama installed with the nomic-embed-text model pulled