OpenClaw plugin adds persistent memory with Engram server

A developer created a TypeScript plugin that connects OpenClaw agents to Engram, a lightweight Go-based memory server that stores structured observations in SQLite with FTS5 full-text search. This provides long-term memory for agents that survives restarts, compactions, and session ends.
How it works
The plugin intercepts incoming messages before each agent turn, extracts keywords, searches Engram, and injects relevant memories into the prompt automatically. This happens through a progressive fallback search: FTS5 uses AND logic, so the system drops keywords one by one until something matches. Results are scored by BM25 relevance, and the plugin skips anything already injected in the session to avoid repeated context.
What agents save
Memories aren't chat dumps but typed observations with categories like decision, bugfix, config, procedure, discovery, and pattern. These are tagged with projects and topic keys. When an agent saves something with the same topic_key as an existing memory, it updates instead of duplicating, allowing knowledge to evolve in place.
Examples of what gets stored include infrastructure preferences and constraints, service credentials and CLI wrappers for each environment, port reservations and deployment conventions, and step-by-step procedures for recurring tasks.
Technical details
The plugin is approximately 750 lines of TypeScript and gives agents 11 tools, 4 lifecycle hooks, and a CLI. It uses the engram_* namespace to coexist with OpenClaw's built-in Markdown memory without conflicts.
Key implementation details:
- Strips channel metadata (Mattermost/Telegram framing, timestamps) before searching to avoid polluted results
- Removes stop words and extracts meaningful keywords
- Dynamically sizes snippets: 1 result gets more detail, 5 results get shorter summaries
- Injects everything with observation IDs so agents can call
engram_getfor full content
Setup requirements
- Install Engram:
brew install gentleman-programming/tap/engramor grab the binary - Run
engram serve(default port 7437, SQLite database, zero config) - Clone the plugin and use
npmfor installation - Set
tools.profile: "full"in your config to make plugin tools visible to agents
Problems encountered and solutions
- FTS5 AND logic: Searching "kubernetes cluster configuration" returns nothing if any single term isn't indexed. Fixed with progressive keyword fallback.
- Channel metadata in prompts: Messages from Mattermost arrive with framing that pollutes searches. Solution is to strip metadata first.
- Plugin tools invisible to agents: OpenClaw's
tools.profile: "coding"filters out plugin-registered tools. Fix istools.profile: "full".
📖 Read the full source: r/openclaw
👀 See Also

Fewshell: A Self-Hosted SSH Copilot That Refuses to Run Commands Without Human Approval
Fewshell is a mobile+desktop SSH copilot with mandatory human approval for every command – no setting to enable auto-approval. Built by an ex-Amazon AI SDE working on AI safety research.

ARP: Stateless WebSocket Relay for Autonomous Agent Communication
ARP (Agent Relay Protocol) is a stateless WebSocket relay for autonomous agent communication featuring Ed25519 identity, HPKE encryption per RFC 9180, binary TLV framing, and 33 bytes overhead per message. No accounts or registration required—just generate a keypair and connect.

Dart AI productivity app review with OpenClaw integration
A user reports switching from Things to Dart AI for productivity, finding it better for implementing Getting Things Done methodology with full OpenClaw access, despite UI issues and initial setup complexity.

Using a Local LLM as a Claude Code Subagent to Reduce Context Usage
A developer shares a method to use Claude Code to delegate tasks to a local LLM via LM Studio's API, keeping file content out of Claude's context. The approach uses a ~120-line Python script with tool-calling to read files locally and return summaries.