← Back to Skills Marketplace
jpengcheng523-netizen

Elite Longterm Memory

by jpengcheng523-netizen · GitHub ↗ · v1.2.3 · MIT-0
cross-platform ⚠ suspicious
131
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install jpeng-elite-memory
Description
Ultimate AI agent memory system for Cursor, Claude, ChatGPT & Copilot. WAL protocol + vector search + git-notes + cloud backup. Never lose context again. Vib...
README (SKILL.md)

Elite Longterm Memory 🧠

The ultimate memory system for AI agents. Combines 6 proven approaches into one bulletproof architecture.

Never lose context. Never forget decisions. Never repeat mistakes.

Architecture Overview

┌─────────────────────────────────────────────────────────────────┐
│                    ELITE LONGTERM MEMORY                        │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  ┌─────────────┐  ┌─────────────┐  ┌─────────────┐             │
│  │   HOT RAM   │  │  WARM STORE │  │  COLD STORE │             │
│  │             │  │             │  │             │             │
│  │ SESSION-    │  │  LanceDB    │  │  Git-Notes  │             │
│  │ STATE.md    │  │  Vectors    │  │  Knowledge  │             │
│  │             │  │             │  │  Graph      │             │
│  │ (survives   │  │ (semantic   │  │ (permanent  │             │
│  │  compaction)│  │  search)    │  │  decisions) │             │
│  └─────────────┘  └─────────────┘  └─────────────┘             │
│         │                │                │                     │
│         └────────────────┼────────────────┘                     │
│                          ▼                                      │
│                  ┌─────────────┐                                │
│                  │  MEMORY.md  │  ← Curated long-term           │
│                  │  + daily/   │    (human-readable)            │
│                  └─────────────┘                                │
│                          │                                      │
│                          ▼                                      │
│                  ┌─────────────┐                                │
│                  │ SuperMemory │  ← Cloud backup (optional)     │
│                  │    API      │                                │
│                  └─────────────┘                                │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

The 5 Memory Layers

Layer 1: HOT RAM (SESSION-STATE.md)

From: bulletproof-memory

Active working memory that survives compaction. Write-Ahead Log protocol.

# SESSION-STATE.md — Active Working Memory

## Current Task
[What we're working on RIGHT NOW]

## Key Context
- User preference: ...
- Decision made: ...
- Blocker: ...

## Pending Actions
- [ ] ...

Rule: Write BEFORE responding. Triggered by user input, not agent memory.

Layer 2: WARM STORE (LanceDB Vectors)

From: lancedb-memory

Semantic search across all memories. Auto-recall injects relevant context.

# Auto-recall (happens automatically)
memory_recall query="project status" limit=5

# Manual store
memory_store text="User prefers dark mode" category="preference" importance=0.9

Layer 3: COLD STORE (Git-Notes Knowledge Graph)

From: git-notes-memory

Structured decisions, learnings, and context. Branch-aware.

# Store a decision (SILENT - never announce)
python3 memory.py -p $DIR remember '{"type":"decision","content":"Use React for frontend"}' -t tech -i h

# Retrieve context
python3 memory.py -p $DIR get "frontend"

Layer 4: CURATED ARCHIVE (MEMORY.md + daily/)

From: OpenClaw native

Human-readable long-term memory. Daily logs + distilled wisdom.

workspace/
├── MEMORY.md              # Curated long-term (the good stuff)
└── memory/
    ├── 2026-01-30.md      # Daily log
    ├── 2026-01-29.md
    └── topics/            # Topic-specific files

Layer 5: CLOUD BACKUP (SuperMemory) — Optional

From: supermemory

Cross-device sync. Chat with your knowledge base.

export SUPERMEMORY_API_KEY="your-key"
supermemory add "Important context"
supermemory search "what did we decide about..."

Layer 6: AUTO-EXTRACTION (Mem0) — Recommended

NEW: Automatic fact extraction

Mem0 automatically extracts facts from conversations. 80% token reduction.

npm install mem0ai
export MEM0_API_KEY="your-key"
const { MemoryClient } = require('mem0ai');
const client = new MemoryClient({ apiKey: process.env.MEM0_API_KEY });

// Conversations auto-extract facts
await client.add(messages, { user_id: "user123" });

// Retrieve relevant memories
const memories = await client.search(query, { user_id: "user123" });

Benefits:

  • Auto-extracts preferences, decisions, facts
  • Deduplicates and updates existing memories
  • 80% reduction in tokens vs raw history
  • Works across sessions automatically

Quick Setup

1. Create SESSION-STATE.md (Hot RAM)

cat > SESSION-STATE.md \x3C\x3C 'EOF'
# SESSION-STATE.md — Active Working Memory

This file is the agent's "RAM" — survives compaction, restarts, distractions.

## Current Task
[None]

## Key Context
[None yet]

## Pending Actions
- [ ] None

## Recent Decisions
[None yet]

---
*Last updated: [timestamp]*
EOF

2. Enable LanceDB (Warm Store)

In ~/.openclaw/openclaw.json:

{
  "memorySearch": {
    "enabled": true,
    "provider": "openai",
    "sources": ["memory"],
    "minScore": 0.3,
    "maxResults": 10
  },
  "plugins": {
    "entries": {
      "memory-lancedb": {
        "enabled": true,
        "config": {
          "autoCapture": false,
          "autoRecall": true,
          "captureCategories": ["preference", "decision", "fact"],
          "minImportance": 0.7
        }
      }
    }
  }
}

3. Initialize Git-Notes (Cold Store)

cd ~/clawd
git init  # if not already
python3 skills/git-notes-memory/memory.py -p . sync --start

4. Verify MEMORY.md Structure

# Ensure you have:
# - MEMORY.md in workspace root
# - memory/ folder for daily logs
mkdir -p memory

5. (Optional) Setup SuperMemory

export SUPERMEMORY_API_KEY="your-key"
# Add to ~/.zshrc for persistence

Agent Instructions

On Session Start

  1. Read SESSION-STATE.md — this is your hot context
  2. Run memory_search for relevant prior context
  3. Check memory/YYYY-MM-DD.md for recent activity

During Conversation

  1. User gives concrete detail? → Write to SESSION-STATE.md BEFORE responding
  2. Important decision made? → Store in Git-Notes (SILENTLY)
  3. Preference expressed?memory_store with importance=0.9

On Session End

  1. Update SESSION-STATE.md with final state
  2. Move significant items to MEMORY.md if worth keeping long-term
  3. Create/update daily log in memory/YYYY-MM-DD.md

Memory Hygiene (Weekly)

  1. Review SESSION-STATE.md — archive completed tasks
  2. Check LanceDB for junk: memory_recall query="*" limit=50
  3. Clear irrelevant vectors: memory_forget id=\x3Cid>
  4. Consolidate daily logs into MEMORY.md

The WAL Protocol (Critical)

Write-Ahead Log: Write state BEFORE responding, not after.

Trigger Action
User states preference Write to SESSION-STATE.md → then respond
User makes decision Write to SESSION-STATE.md → then respond
User gives deadline Write to SESSION-STATE.md → then respond
User corrects you Write to SESSION-STATE.md → then respond

Why? If you respond first and crash/compact before saving, context is lost. WAL ensures durability.

Example Workflow

User: "Let's use Tailwind for this project, not vanilla CSS"

Agent (internal):
1. Write to SESSION-STATE.md: "Decision: Use Tailwind, not vanilla CSS"
2. Store in Git-Notes: decision about CSS framework
3. memory_store: "User prefers Tailwind over vanilla CSS" importance=0.9
4. THEN respond: "Got it — Tailwind it is..."

Maintenance Commands

# Audit vector memory
memory_recall query="*" limit=50

# Clear all vectors (nuclear option)
rm -rf ~/.openclaw/memory/lancedb/
openclaw gateway restart

# Export Git-Notes
python3 memory.py -p . export --format json > memories.json

# Check memory health
du -sh ~/.openclaw/memory/
wc -l MEMORY.md
ls -la memory/

Why Memory Fails

Understanding the root causes helps you fix them:

Failure Mode Cause Fix
Forgets everything memory_search disabled Enable + add OpenAI key
Files not loaded Agent skips reading memory Add to AGENTS.md rules
Facts not captured No auto-extraction Use Mem0 or manual logging
Sub-agents isolated Don't inherit context Pass context in task prompt
Repeats mistakes Lessons not logged Write to memory/lessons.md

Solutions (Ranked by Effort)

1. Quick Win: Enable memory_search

If you have an OpenAI key, enable semantic search:

openclaw configure --section web

This enables vector search over MEMORY.md + memory/*.md files.

2. Recommended: Mem0 Integration

Auto-extract facts from conversations. 80% token reduction.

npm install mem0ai
const { MemoryClient } = require('mem0ai');

const client = new MemoryClient({ apiKey: process.env.MEM0_API_KEY });

// Auto-extract and store
await client.add([
  { role: "user", content: "I prefer Tailwind over vanilla CSS" }
], { user_id: "ty" });

// Retrieve relevant memories
const memories = await client.search("CSS preferences", { user_id: "ty" });

3. Better File Structure (No Dependencies)

memory/
├── projects/
│   ├── strykr.md
│   └── taska.md
├── people/
│   └── contacts.md
├── decisions/
│   └── 2026-01.md
├── lessons/
│   └── mistakes.md
└── preferences.md

Keep MEMORY.md as a summary (\x3C5KB), link to detailed files.

Immediate Fixes Checklist

Problem Fix
Forgets preferences Add ## Preferences section to MEMORY.md
Repeats mistakes Log every mistake to memory/lessons.md
Sub-agents lack context Include key context in spawn task prompt
Forgets recent work Strict daily file discipline
Memory search not working Check OPENAI_API_KEY is set

Troubleshooting

Agent keeps forgetting mid-conversation: → SESSION-STATE.md not being updated. Check WAL protocol.

Irrelevant memories injected: → Disable autoCapture, increase minImportance threshold.

Memory too large, slow recall: → Run hygiene: clear old vectors, archive daily logs.

Git-Notes not persisting: → Run git notes push to sync with remote.

memory_search returns nothing: → Check OpenAI API key: echo $OPENAI_API_KEY → Verify memorySearch enabled in openclaw.json


Links


Built by @NextXFrontier — Part of the Next Frontier AI toolkit

Usage Guidance
This package appears to implement local, file-based agent memory and is largely coherent with that purpose, but exercise caution before enabling optional integrations. Actionable checks before installing: - Verify provenance: the registry Owner ID and the _meta.json ownerId do not match and the skill metadata showed no homepage; confirm the upstream GitHub repo and author before trusting it. - Do NOT export or provide MEM0_API_KEY or SUPERMEMORY_API_KEY unless you trust those third-party services — they would receive your agent's memory content (sensitive data). - Review the included files (bin/elite-memory.js, README, SKILL.md) yourself; the bundle is small and easy to inspect. The CLI only writes markdown files and checks for local LanceDB paths. - Be aware the skill instructs editing ~/.openclaw/openclaw.json to enable a memory plugin — back up that file first and inspect changes before applying them. - Note some examples reference external scripts (python3 memory.py) that are not bundled; these are integration examples, not hidden code. If you need higher assurance, ask the publisher for a canonical repository URL and a signed release, or run the package in an isolated environment first.
Capability Assessment
Purpose & Capability
The name/description (agent long-term memory) matches the files and runtime behavior: creating SESSION-STATE.md, MEMORY.md, a memory/ directory, and CLI helpers is coherent. Requiring OPENAI_API_KEY for semantic search is reasonable. Minor provenance discrepancies: the registry Owner ID (kn751...) differs from _meta.json ownerId (kn7ewy...), and the skill metadata lists no homepage while package.json points to a GitHub repo — these inconsistencies weaken trust but do not by themselves indicate malicious behavior.
Instruction Scope
SKILL.md instructs the agent to create and modify workspace files (SESSION-STATE.md, MEMORY.md, memory/YYYY-MM-DD.md) and edit agent config (e.g., ~/.openclaw/openclaw.json) to enable LanceDB — all expected for a memory system. It also recommends optional external services (Mem0, SuperMemory) and shows commands that would send memory data to those third-party APIs; those are explicit but represent potential data exfiltration if used. Some referenced commands/files (e.g., python3 memory.py usage) are not included in the package — they appear to be integrations or examples rather than bundled code.
Install Mechanism
There is no automatic install script in the registry metadata (instruction-only). The package includes a small CLI (bin/elite-memory.js) and a package.json with an optional dependency (mem0ai). Nothing in the included files downloads or executes remote code. The only install action a user might take is optional 'npm install mem0ai' (explicit in docs). No suspicious download URLs or archive extraction are present.
Credentials
The skill declares a single required env var: OPENAI_API_KEY, which is proportionate for OpenAI-based semantic search. The SKILL.md and README also instruct users to export optional secrets (MEM0_API_KEY, SUPERMEMORY_API_KEY) for third-party integrations; those are optional but powerful (would allow sending memory data to external services). The skill does not request unrelated credentials, but users should be aware optional integrations will require additional keys.
Persistence & Privilege
always:false and normal autonomous invocation settings are fine. The skill writes files in the workspace and suggests editing the user's agent config (~/.openclaw/openclaw.json) to enable LanceDB — this is reasonable for a memory system. It does not request elevated or system-wide privileges, nor does it modify other skills' configuration beyond advising the user to enable a plugin.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install jpeng-elite-memory
  3. After installation, invoke the skill by name or use /jpeng-elite-memory
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.3
Ultimate AI agent memory system
Metadata
Slug jpeng-elite-memory
Version 1.2.3
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Elite Longterm Memory?

Ultimate AI agent memory system for Cursor, Claude, ChatGPT & Copilot. WAL protocol + vector search + git-notes + cloud backup. Never lose context again. Vib... It is an AI Agent Skill for Claude Code / OpenClaw, with 131 downloads so far.

How do I install Elite Longterm Memory?

Run "/install jpeng-elite-memory" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Elite Longterm Memory free?

Yes, Elite Longterm Memory is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Elite Longterm Memory support?

Elite Longterm Memory is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Elite Longterm Memory?

It is built and maintained by jpengcheng523-netizen (@jpengcheng523-netizen); the current version is v1.2.3.

💬 Comments