Victor Memory Hub

Four-tier memory architecture with automated Dreaming pipeline, three-way synchronization, Active Memory recall, and two-stage auto-extraction.

Overview

Automated Pipelines

Memory Flow (Unified Daily Pipeline)

agent_end → MemOS Cloud (cloud extraction)
              ↓
    ┌─ 18:00 sync-pull (Cloud → local cache) ─┐
    │  18:30 auto-memory.py                    │
    │  → Stage 1: ARCHIVE.md (SHA-256 dedup)   │
    │  → Stage 2: MEMORY.md (one-line summary) │
    │                                           │
    │  20:00 sync-push + reindex                │
    │  22:00 session-extract.py                 │
    │  → Pass 1: .learnings/ERRORS.md           │
    │  → Pass 2: memory/YYYY-MM-DD.md           │
    │  → archive analyzed → trash               │
    └───────────────────────────────────────────┘

before_agent_start → MemOS Cloud recall
                  + Active Memory sub-agent
                  + memory-core (bge-m3 + BM25)
              ↓
        Layered context injected before reply

Scripts

Setup

One-command auto-setup

bash scripts/auto-setup.sh

Options

bash scripts/auto-setup.sh --skip-ollama   # Skip Ollama install
bash scripts/auto-setup.sh --skip-memos    # Skip MemOS Cloud
bash scripts/auto-setup.sh --dry-run       # Preview only

Manual setup

See references/setup-guide.md for step-by-step manual configuration.

When to Use

• Setting up OpenClaw memory for the first time
• Configuring memory-core plugin with local Ollama embedding
• Installing MemOS Cloud plugin for cross-device sync
• Enabling Active Memory for pre-reply context injection
• Setting up auto-memory pipeline for MEMORY.md curation
• Installing cross-platform-writer for cross-OS file compatibility
• Configuring automatic Dreaming and promotion pipelines
• Setting up three-way sync between cloud, files, and vector DB

Plugin Conflicts

❌ subconscious-personality-guardian ↔ memory-core

Incompatible. Both use the same OpenClaw memory slot.

Fix: Disable in openclaw.json:

{
  "plugins": {
    "disabled": ["subconscious-personality-guardian"],
    "deny": ["subconscious-personality-guardian"]
  }
}

✅ memory-core + MemOS Cloud

Compatible — designed to work in layers.

User message → MemOS Cloud (static facts) → memory-core (recent context)

✅ Active Memory + MemOS Cloud + memory-core

Compatible — triple-layer recall.

User message
  → Active Memory sub-agent (searches all memory stores)
  → MemOS Cloud (injects long-term facts & preferences)
  → memory-core (semantic + BM25 hybrid retrieval)
  → Agent receives layered context

✅ auto-memory + MemOS Cloud + memos-extractor

Designed to work together. MemOS captures at agent_end, syncs to local files, then auto-memory reads those files for MEMORY.md curation. v1.10 adds a second channel: memos-extractor-0.6b API (MemOS self-developed model) returns structured facts + preferences, cross-validated against qwen3 output.

Components

1. Memory Plugins (L0)

See references/architecture.md for full configuration.

2. Memory Files (L1 + L2)

~/.openclaw/workspace/
├── memory/
│   ├── YYYY-MM-DD.md          # Daily working memory (auto-indexed)
│   ├── MEMORY_INDEX.md        # Vector BM25 cluster summaries
│   └── .sync-*.json           # Sync state files
├── MEMORY.md                  # Long-term memory index (~90 lines)
├── ARCHIVE.md                 # Detailed archive (~220 lines, ← bidirectional refs)
├── AGENTS.md                  # Runtime context + memory rules
└── user_workspace/
    ├── memos-cloud-cache/         # Cloud-pulled memory (isolated from index)
    │   └── memos-cloud-*.md
    ├── scripts/
    │   └── sync-*.py              # Sync scripts (pull/push/vector)
    └── skills/
        └── victor-memory-hub/   # Installed from ClawHub
            └── scripts/           # Pipeline scripts (auto-memory, session-extract, etc.)

3. Pipeline Scripts (in victor-memory-hub/scripts/)

• auto_memory_extract.py — v3 two-stage pipeline (ARCHIVE.md → MEMORY.md)
• session-extract.py — Session JSONL scan → .learnings/ + memory/
• seed-facts-db.py — Initialize facts.sqlite from ARCHIVE.md
• facts_activation.py — Hebbian activation + daily decay
• daily-memory-pipeline.sh — 6-stage unified daily pipeline
• write_file.py — Cross-platform text file writer
• auto-setup.sh — One-command Ollama + memory-core + MemOS Cloud setup

See references/sync-api.md for MemOS Cloud API details.

File Reference

• references/architecture.md — Detailed architecture documentation
• references/setup-guide.md — Complete manual setup guide with templates
• references/sync-api.md — MemOS Cloud API reference
• scripts/auto-setup.sh — One-command interactive setup
• scripts/auto_memory_extract.py — auto-memory v2 script
• scripts/write_file.py — Cross-platform text file writer
• scripts/auto_memory_extract.py — v3 two-stage memory extraction