Mengram Memory#

Human-like long-term memory for your OpenClaw agent. Remembers facts, events, and workflows across all sessions and channels.

What This Skill Does#

Mengram gives you 3 types of memory that work together:

• Semantic Memory — facts about the user (preferences, relationships, work, habits)
• Episodic Memory — events with timestamps and outcomes (meetings, trips, decisions)
• Procedural Memory — learned workflows with success/failure tracking (how-to steps)
• Experience-Driven Procedures — workflows that self-improve: failures trigger automatic evolution, repeated successes auto-create new procedures

All memory persists across sessions and channels. What you learn on WhatsApp is available on Discord.

Tools#

This skill uses Bash to run scripts in {baseDir}/scripts/.

When To Use#

ALWAYS search memory before answering questions about the user, their preferences, their history, or anything personal. This is critical — check memory first, then respond.

Save to memory after:

• The user shares personal information (name, preferences, habits, relationships)
• A task or event is completed (booking, deployment, purchase)
• A multi-step workflow is finished successfully or fails
• The user corrects you or provides new context

Record procedure feedback after:

• A known workflow succeeds — run mengram-feedback.sh with true
• A known workflow fails — run mengram-feedback.sh with false and describe what went wrong. This triggers automatic procedure evolution — the procedure improves itself.

Get profile when:

• Starting a new session or conversation
• The user asks "what do you know about me"
• You need comprehensive context about the user

Scripts#

1. Search Memory#

Search all 3 memory types for relevant context. Do this before answering personal questions.

bash

bash {baseDir}/scripts/mengram-search.sh "search query here"

Returns facts, past events, and known workflows matching the query. Use specific queries — "coffee preferences" not "stuff about user".

2. Save to Memory#

Save conversation messages so Mengram can extract facts, events, and procedures automatically.

bash

bash {baseDir}/scripts/mengram-add.sh "user said: I'm allergic to peanuts and my meeting with Sarah went well yesterday"

You can pass multiple messages. Mengram's AI automatically extracts:

• Facts → semantic memory ("user is allergic to peanuts")
• Events → episodic memory ("meeting with Sarah, yesterday, went well")
• Procedures → procedural memory (if workflow steps are described)

3. Get Cognitive Profile#

Get a comprehensive portrait of the user — who they are, what they know, recent events, known workflows.

bash

bash {baseDir}/scripts/mengram-profile.sh

Returns a full context block you can use to personalize responses.

4. Save Workflow#

After completing a multi-step task, save it as a reusable procedure with success/failure tracking.

bash

bash {baseDir}/scripts/mengram-workflow.sh "Resolved billing issue: 1) Checked subscription status 2) Found expired card 3) Sent renewal link 4) User confirmed payment"

Next time a similar task comes up, mengram-search.sh will return this workflow with its success rate.

5. Procedure Feedback (Experience-Driven)#

Record success or failure for a procedure. On failure with context, the procedure automatically evolves — AI analyzes what went wrong and creates an improved version.

bash

# Success
bash {baseDir}/scripts/mengram-feedback.sh "procedure-id" true

# Failure — triggers evolution
bash {baseDir}/scripts/mengram-feedback.sh "procedure-id" false "OOM error on step 3, forgot to increase memory limit" 3

Arguments: <procedure-id> <true|false> [failure context] [failed_at_step]

The procedure ID is returned in search results. When evolution triggers, the procedure gets a new version with improved steps — automatically.

6. List Procedures#

View all learned procedures, or drill into a specific one to see version history and evolution log.

bash

# List all
bash {baseDir}/scripts/mengram-procedures.sh

# Specific procedure with version history
bash {baseDir}/scripts/mengram-procedures.sh "procedure-id"

Shows procedure name, steps, success/failure counts, version number, and full evolution history.

7. Setup Check#

Verify the Mengram connection is working:

bash

bash {baseDir}/scripts/mengram-setup.sh

Recommended Behavior#

1. Start of session: Run mengram-profile.sh to load user context
2. User asks something personal: Run mengram-search.sh "topic" before answering
3. User shares new info: Run mengram-add.sh with the relevant messages
4. After completing a task: Run mengram-workflow.sh with the steps taken
5. Task succeeded using a known procedure: Run mengram-feedback.sh <id> true
6. Task failed using a known procedure: Run mengram-feedback.sh <id> false "what went wrong" <step> — this evolves the procedure
7. Check learned procedures: Run mengram-procedures.sh to see all workflows with versions
8. Periodically: Run mengram-add.sh with recent conversation highlights to keep memory updated

Examples#

• "What's my favorite restaurant?" → mengram-search.sh "favorite restaurant"
• "Book the usual" → mengram-search.sh "booking usual preferences" to find what "the usual" means
• "I just switched to a new phone, Galaxy S26" → mengram-add.sh "user switched to Samsung Galaxy S26"
• "Remember that I'm vegetarian" → mengram-add.sh "user is vegetarian"
• User asks "what do you know about me?" → mengram-profile.sh
• Deploy succeeded → mengram-feedback.sh "proc-id" true
• Deploy failed at step 3 → mengram-feedback.sh "proc-id" false "forgot migrations" 3 → procedure auto-evolves
• "Show me my workflows" → mengram-procedures.sh

Configuration#

Set in ~/.openclaw/openclaw.json:

json

{
  "skills": {
    "entries": {
      "mengram-memory": {
        "enabled": true,
        "env": {
          "MENGRAM_API_KEY": "om-your-api-key-here"
        }
      }
    }
  }
}

Get your free API key at https://mengram.io

Security & Privacy#

• External endpoint: https://mengram.io/v1/* (only)
• Data sent: conversation text for memory extraction, search queries, procedure feedback
• Data stored: extracted facts, events, procedures (with version history) on Mengram servers (PostgreSQL + pgvector)
• Environment variables accessed: MENGRAM_API_KEY (only)
• Local files read/written: none

Trust Statement: By using this skill, conversation data is sent to mengram.io for memory extraction and storage. Only install if you trust Mengram with your conversation data. Mengram is open-source: https://github.com/AiBaizhanov/mengram