elite-longterm-memory

Store and retrieve persistent agent context across sessions with layered memory.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Jaykaijack/openclaw-backup --skill elite-longterm-memory-jaykaijack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: elite-longterm-memory
Source: https://github.com/Jaykaijack/openclaw-backup/tree/main/skills/elite-longterm-memory
Command: npx skills add https://github.com/Jaykaijack/openclaw-backup --skill elite-longterm-memory-jaykaijack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI agents often lose important context across tasks, sessions, or restarts. Elite Longterm Memory provides a durable, multi-layer memory architecture to preserve decisions, preferences, and knowledge.

Core Features & Use Cases

  • WAL-protected hot RAM, warm semantic store, and cold knowledge graph for durable context.
  • LanceDB-based vector search enables instant recall across tasks and projects.
  • Git-Notes knowledge graph with branch-aware decisions for auditability and collaboration.
  • MEMORY.md curated archive plus daily logs for long-term reflection; optional cloud backup for cross-device sync.
  • Mem0 auto-extraction to reduce context size and surface relevant memories automatically.

Quick Start

Initialize in your workspace with npx elite-longterm-memory init.

Frequently Asked Questions about elite-longterm-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add persistent long-term memory to an AI agent across sessions?

You can add persistent long-term memory to an AI agent by using a multi-layer architecture that stores and retrieves context across sessions. This involves hot RAM, warm semantic stores, and cold knowledge graphs to preserve decisions and enable durable recall.

What's the best way to restore context for an AI agent after a restart?

Restoring context for an AI agent after a restart requires write-ahead logging (WAL) and vector search. This combination guarantees durability and accessibility, enabling rapid context restoration from warm stores and cold knowledge graphs without losing previous decisions.

How does vector search work for retrieving agent memories in coding workflows?

Vector search retrieves agent memories by using LanceDB to index and query persistent context across tasks and projects. This enables instant recall of decisions, preferences, and knowledge stored in the warm semantic store during coding workflows.

Can I use a knowledge graph for AI agent memory and branch-aware decisions?

Yes, you can use a Git-Notes knowledge graph to store branch-aware decisions for AI agents. This approach provides auditability and collaboration by structuring persistent context alongside your coding workflows and daily logs.

How do I initialize a unified memory system in my workspace?

To initialize a unified memory system in your workspace, run the command `npx elite-longterm-memory init`. This sets up the multi-layer memory architecture, including hot RAM, warm store, cold knowledge graph, and optional cloud backup.

Does AI agent memory support cloud backup for cross-device sync?

Yes, AI agent memory supports optional cloud backup for cross-device sync. This ensures that durable context, decision logs, and the structured knowledge graph remain accessible and synchronized across different devices and sessions.