simple-memory-skill

Zero-dependency AI memory system. No API keys needed. Pure local storage with smart search. Works everywhere.

Simple Local Memory 🧠

The zero-dependency memory system for AI agents.

No API keys. No external services. No cloud dependencies. Just pure local storage with intelligent search.

Architecture

text

┌─────────────────────────────────────────────────┐
│          SIMPLE LOCAL MEMORY                    │
├─────────────────────────────────────────────────┤
│                                                 │
│  ┌─────────────┐  ┌─────────────┐             │
│  │   HOT RAM   │  │  COLD STORE │             │
│  │             │  │             │             │
│  │ SESSION-    │  │  Indexed    │             │
│  │ STATE.json  │  │  Memories   │             │
│  │             │  │  (JSON +    │             │
│  │ (active     │  │   Search)   │             │
│  │  context)   │  │             │             │
│  └─────────────┘  └─────────────┘             │
│         │                │                     │
│         └────────────────┼─────────────────┘   │
│                          ▼                      │
│                  ┌─────────────┐                │
│                  │ MEMORY.md   │ ← Human        │
│                  │ + daily/    │   readable     │
│                  └─────────────┘                │
│                                                 │
└─────────────────────────────────────────────────┘

The 3 Memory Layers

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

Fast, active working memory

json

{
  "current_task": "...",
  "key_context": ["...", "..."],
  "pending_actions": ["...", "..."],
  "recent_decisions": ["..."],
  "last_updated": "2026-03-15T10:30:00Z"
}

Benefits:

• Fast JSON read/write
• Survives compaction
• Easy to parse programmatically

Layer 2: COLD STORE (Indexed Memories)

Persistent, searchable memory

bash

# Store a memory
memory-store --type preference --content "User prefers dark mode" --importance 0.9

# Search memories
memory-search "what did user say about CSS"

# List recent
memory-list --limit 10

Storage: memories/ directory with indexed JSON files

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

Human-readable long-term memory

text

workspace/
├── MEMORY.md              # Curated insights
├── SESSION-STATE.json     # Active context
└── memories/
    ├── 2026-03-15.json    # Daily memory dump
    ├── preferences.json   # User preferences
    ├── decisions.json     # Key decisions
    └── lessons.json       # Lessons learned

Quick Setup

Step 1: Initialize

bash

npm install -g simple-local-memory
cd your-project
memory-init

This creates:

• SESSION-STATE.json - Active working memory
• MEMORY.md - Long-term curated memory
• memories/ - Directory for memory storage

Step 2: Use with Your AI Agent

For Claude Code:

markdown

# Add to your custom instructions

When I give you important information:
1. Write it to SESSION-STATE.json FIRST
2. Then store it using memory-store
3. Then respond to me

When starting a conversation:
1. Read SESSION-STATE.json
2. Search relevant memories with memory-search
3. Check MEMORY.md for context

For ChatGPT/Cursor: Add to your system prompt:

text

You have access to local memory tools:
- memory-store: Save important information
- memory-search: Find relevant past context
- Read SESSION-STATE.json before responding
- Update SESSION-STATE.json when user shares preferences

Memory CLI Commands

bash

# Initialize memory system
memory-init

# Store a memory
memory-store --type preference --content "User loves TypeScript" --importance 0.9

# Search memories
memory-search "TypeScript preferences"

# List recent memories
memory-list --limit 10 --type preference

# Show memory stats
memory-stats

# Export memories
memory-export --format json --output backup.json

# Import memories
memory-import --file backup.json

WAL Protocol (Write-Ahead Logging)

CRITICAL: Write to memory BEFORE responding

Trigger	Action
User states preference	Update SESSION-STATE.json → Store → Respond
User makes decision	Update SESSION-STATE.json → Store → Respond
User gives deadline	Update SESSION-STATE.json → Store → Respond
User corrects you	Update SESSION-STATE.json → Store → Respond

Why? If response crashes before saving, context is lost.

Memory Storage Format

memories/YYYY-MM-DD.json

json

{
  "date": "2026-03-15",
  "memories": [
    {
      "id": "uuid",
      "type": "preference|decision|fact|lesson",
      "content": "User prefers dark mode",
      "importance": 0.9,
      "tags": ["ui", "preferences"],
      "timestamp": "2026-03-15T10:30:00Z",
      "context": "Discussed during UI setup"
    }
  ]
}

memories/preferences.json

json

{
  "preferences": [
    {
      "key": "css_framework",
      "value": "Tailwind",
      "set_at": "2026-03-15T10:30:00Z",
      "reason": "User prefers over vanilla CSS"
    }
  ]
}

memories/decisions.json

json

{
  "decisions": [
    {
      "id": "uuid",
      "title": "Use React for frontend",
      "reason": "User requested component-based architecture",
      "made_at": "2026-03-15T10:30:00Z",
      "status": "active"
    }
  ]
}

Search Algorithm

TF-IDF based local search:

1. Tokenize query and memories
2. Calculate term frequency
3. Rank by relevance + importance + recency
4. Return top N results

javascript

// Example search logic
function searchMemories(query, limit = 5) {
  const queryTokens = tokenize(query);
  const allMemories = loadAllMemories();

  const scored = allMemories.map(memory => {
    const score = calculateTFIDF(queryTokens, memory.content);
    const recencyBoost = calculateRecencyBoost(memory.timestamp);
    const importanceBoost = memory.importance || 0.5;

    return {
      ...memory,
      totalScore: score + recencyBoost + importanceBoost
    };
  });

  return scored
    .sort((a, b) => b.totalScore - a.totalScore)
    .slice(0, limit);
}

Example Workflow

text

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

Agent process:
1. Update SESSION-STATE.json with decision
2. Execute: memory-store --type decision --content "Use Tailwind, not vanilla CSS" --importance 0.9
3. Execute: memory-store --type preference --content "User prefers Tailwind over vanilla CSS" --importance 0.95
4. THEN respond: "Got it — Tailwind it is. I've saved this preference."

Memory Categories

Type	When to Use	Importance
preference	User expresses like/dislike	0.8-1.0
decision	Project decision made	0.9-1.0
fact	Important information	0.6-0.8
lesson	Learned from mistake	0.9-1.0
context	Background info	0.4-0.6

Maintenance

Daily

bash

# Check memory health
memory-stats

# Review today's memories
memory-list --date today

Weekly

bash

# Archive old memories
memory-archive --days 7

# Clean duplicates
memory-deduplicate

# Update MEMORY.md with insights
# (Manual: review memories/ and add to MEMORY.md)

Monthly

bash

# Export backup
memory-export --format json --output monthly-backup.json

# Clear old daily files
memory-cleanup --days 30

Memory Hygiene Tips

1. Be specific - "User likes dark mode" > "User has preference"
2. Add context - Why was this decision made?
3. Use importance - Not everything is 1.0
4. Tag properly - Helps with retrieval
5. Archive regularly - Keep SESSION-STATE.json small

Troubleshooting

Search returns nothing: → Check memories/ directory exists → Verify JSON files are valid → Try broader search terms

SESSION-STATE.json grows too large: → Move old items to memory-store → Archive completed tasks → Keep only active context

Memories not being saved: → Check file permissions → Verify disk space → Check JSON syntax

Advanced Features

Memory Relationships

json

{
  "id": "uuid",
  "content": "Use React for frontend",
  "related_to": ["uuid-of-other-memory"],
  "followed_by": ["uuid-of-decision"]
}

Confidence Scores

json

{
  "confidence": 0.95,
  "source": "explicit_user_statement",
  "verified_count": 3
}

Expiry Dates

json

{
  "expires_at": "2026-04-15T00:00:00Z",
  "auto_archive": true
}

Comparison with elite-longterm-memory

Feature	Elite	Simple Local
API keys required	Yes (OpenAI)	No
External dependencies	LanceDB, Mem0	None
Cloud sync	Yes	No (can add)
Vector search	Yes	TF-IDF local
Auto-extraction	Mem0	Manual/Simple rules
Setup complexity	Medium	Simple
Privacy	Cloud-dependent	100% local
Cost	Free tiers limit	100% free

Migration from elite-longterm-memory

bash

# Export from elite system
memory-export > elite-backup.json

# Convert format
node convert-elite-to-simple.js elite-backup.json > simple-backup.json

# Import to simple system
memory-import --file simple-backup.json

Future Enhancements (Optional)

• Add local embedding models (Transformers.js)
• Add compression for old memories
• Add encryption for sensitive data
• Add sync via GitHub Gist
• Add web UI for memory management

---

No API keys. No cloud. No tracking. Just pure local memory.

Perfect for:

• Privacy-conscious users
• Offline development
• Learning how memory systems work
• Building custom AI agents
• Projects with strict data policies