← 返回 Skills 市场
farmerboybi-bot

Elite Longterm Memory Backup

作者 farmerboybi-bot · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
241
总下载
0
收藏
2
当前安装
1
版本数
在 OpenClaw 中安装
/install elite-longterm-memory-backup
功能描述
Ultimate AI agent memory system for Cursor, Claude, ChatGPT & Copilot. WAL protocol + vector search + git-notes + cloud backup. Never lose context again. Vib...
使用说明 (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

安全使用建议
What to consider before installing: - Verify provenance: the registry metadata, SKILL.md, package.json, and _meta.json show inconsistent versions/IDs and 'Source: unknown' — confirm the publisher and repository (the package.json points to a GitHub repo; inspect it) before trusting the skill. - Local files: the CLI will create SESSION-STATE.md, MEMORY.md, and memory/<date>.md in whatever directory you run it from. These will contain potentially sensitive decisions and context—add them to .gitignore or store them encrypted if needed. - Optional cloud services: SKILL.md demonstrates Mem0 and SuperMemory usage. If you set MEM0_API_KEY or SUPERMEMORY_API_KEY, those services will receive extracted memories. Only provide keys if you trust the service and reviewed its privacy policy; treat those as high-sensitivity credentials. - Minimal privileges: the included bin/elite-memory.js is small and only reads/writes local files and checks a path under HOME; review its code (already included) before running. Avoid installing optional dependencies (mem0ai) unless you intentionally want remote auto-extraction. - Plugin configuration: enabling LanceDB or other agent plugins may require additional configuration/keys—check what data will be sent to OpenAI or other providers when enabling memorySearch. - If you need more assurance: ask the publisher for a signed release or a well-known repository URL, or request that the skill explicitly list optional external env vars (MEM0_API_KEY, SUPERMEMORY_API_KEY) in its registry metadata so their usage is visible up front.
功能分析
Type: OpenClaw Skill Name: elite-longterm-memory-backup Version: 1.0.0 The skill bundle provides a comprehensive memory management system for AI agents using a multi-layered approach (local Markdown files, vector databases, and optional cloud sync). The Node.js CLI tool in `bin/elite-memory.js` performs standard file system operations to initialize workspace files like `SESSION-STATE.md` and `MEMORY.md`. The instructions in `SKILL.md` are well-documented and align with the stated purpose of maintaining persistent context; no evidence of malicious intent, data exfiltration, or harmful prompt injection was found.
能力评估
Purpose & Capability
The code and SKILL.md implement a local memory system (SESSION-STATE.md, MEMORY.md, memory/ daily logs) and point to LanceDB, git-notes, and optional cloud services. Requiring OPENAI_API_KEY is reasonable for an OpenAI-backed memorySearch provider. However, the package and docs also recommend optional services (Mem0, SuperMemory) that would require additional credentials; those are not listed as required in the registry metadata.
Instruction Scope
Runtime instructions and CLI operate on the workspace (create SESSION-STATE.md, MEMORY.md, memory/<date>.md) and suggest editing agent/plugin configs (e.g., ~/.openclaw/openclaw.json, ~/.clawdbot/clawdbot.json). SKILL.md also contains snippets showing use of SUPERMEMORY_API_KEY and MEM0_API_KEY (external services). The instructions do not direct reading of unrelated system files, but they do instruct transmitting data to optional cloud endpoints (Mem0, SuperMemory) which could expose sensitive memory if enabled.
Install Mechanism
This is instruction-first with one small CLI JS file included; there is no install script that downloads arbitrary archives or runs remote code. package.json lists mem0ai as an optional dependency (npm) but nothing is auto-downloaded by the skill metadata. Install risk is low if you don't run 'npm install' for optional deps.
Credentials
Registry metadata declares OPENAI_API_KEY as the required env var (reasonable). But SKILL.md demonstrates and suggests exporting SUPERMEMORY_API_KEY and MEM0_API_KEY for optional cloud sync/auto-extraction. Those additional credentials are not declared as required by the registry. The skill could send user memory to external services if those optional keys are provided—this is a data exposure risk and should be explicitly disclosed in metadata.
Persistence & Privilege
The skill is not marked always:true and does not request system-wide privileges. Its CLI writes files inside the current workspace and checks for a LanceDB path under the user's HOME; it does not modify other skills or global agent configs arbitrarily. Autonomy settings are default.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install elite-longterm-memory-backup
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /elite-longterm-memory-backup 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v1.0.0
- Initial release of elite-longterm-memory-backup, providing an advanced memory system for AI agents. - Combines six complementary memory layers: hot RAM (SESSION-STATE.md), warm store (LanceDB vector semantic search), cold store (git-notes knowledge graph), curated human-readable MEMORY.md, optional SuperMemory cloud backup, and new Mem0 automatic fact extraction. - Follows a Write-Ahead Log (WAL) protocol: always write state before responding, ensuring context is never lost. - Integrates with major AI platforms and tools, supporting cross-device, persistent context and "never forget" workflows. - Includes detailed setup instructions and actionable best practices for memory management and hygiene.
元数据
Slug elite-longterm-memory-backup
版本 1.0.0
许可证 MIT-0
累计安装 2
当前安装数 2
历史版本数 1
常见问题

Elite Longterm Memory Backup 是什么?

Ultimate AI agent memory system for Cursor, Claude, ChatGPT & Copilot. WAL protocol + vector search + git-notes + cloud backup. Never lose context again. Vib... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 241 次。

如何安装 Elite Longterm Memory Backup?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install elite-longterm-memory-backup」即可一键安装,无需额外配置。

Elite Longterm Memory Backup 是免费的吗?

是的,Elite Longterm Memory Backup 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

Elite Longterm Memory Backup 支持哪些平台?

Elite Longterm Memory Backup 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 Elite Longterm Memory Backup?

由 farmerboybi-bot(@farmerboybi-bot)开发并维护,当前版本 v1.0.0。

💬 留言讨论