vps-memory
Access Flo's long-term memory on the VPS (OpenClaw). ALWAYS use when the user says "memory", "memories", "remember", "souviens-toi", "rappelle-toi", "save memory", "search memory", "VPS memory", "OpenClaw", or mentions saving/searching past sessions or knowledge.
Best use case
vps-memory is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Access Flo's long-term memory on the VPS (OpenClaw). ALWAYS use when the user says "memory", "memories", "remember", "souviens-toi", "rappelle-toi", "save memory", "search memory", "VPS memory", "OpenClaw", or mentions saving/searching past sessions or knowledge.
Teams using vps-memory should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/vps-memory/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How vps-memory Compares
| Feature / Agent | vps-memory | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Access Flo's long-term memory on the VPS (OpenClaw). ALWAYS use when the user says "memory", "memories", "remember", "souviens-toi", "rappelle-toi", "save memory", "search memory", "VPS memory", "OpenClaw", or mentions saving/searching past sessions or knowledge.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
<objective> Search or save memories on the VPS via OpenClaw's memory system. </objective> <context> Flo's long-term memory lives on the VPS at `~/.openclaw/workspace/`. **NEVER edit MEMORY.md** — it's curated by OpenClaw. Always create new files in `memory/`. ### Key paths on VPS - MEMORY.md (curated, READ-ONLY): `/root/.openclaw/workspace/MEMORY.md` - Session memories (CREATE HERE): `/root/.openclaw/workspace/memory/` - SQLite index: `/root/.openclaw/memory/main.sqlite` </context> <quick_start> Parse user intent, then run the matching command: **Search memories:** ```bash ssh vps 'cd /root/openclaw && docker compose exec openclaw-gateway node dist/index.js memory search "QUERY"' ``` **Save a new memory:** ```bash ssh vps 'cat > /root/.openclaw/workspace/memory/YYYY-MM-DD-topic.md << '\''EOF'\'' # Session: YYYY-MM-DD (via Claude Code local) ## Topic Content here **Tags:** relevant, tags, here EOF' ``` Then reindex: ```bash ssh vps 'cd /root/openclaw && docker compose exec openclaw-gateway node dist/index.js memory index' ``` <intent_mapping> - "search memory" / "cherche dans ma mémoire" / "tu te souviens" → search - "save memory" / "retiens ça" / "souviens-toi" / "note ça" → save + reindex - "show memories" / "list memories" → search with broad query </intent_mapping> </quick_start> <success_criteria> - Search: returns relevant memory results - Save: file created on VPS + reindex completed successfully </success_criteria>
Related Skills
session-memory
Internal skill. Use cc10x-router for all development tasks.
moai-foundation-memory
Persistent memory across sessions using MCP Memory Server for user preferences, project context, and learned patterns
memorylane
Zero-config persistent memory for Claude with automatic cost savings. Use when you need to remember project context, reduce API token costs, track learned patterns, manage memories across sessions, or curate/clean up memories. Automatically compresses context 6x and saves 84% on API costs. Keywords: memory, remember, recall, context, cost savings, reduce tokens, learn, patterns, insights, curate, clean up memories, review memories.
memory-sync
Guided workflow for maintaining strategic redundancy between Serena memories and project documentation. Use after significant code changes, phase completions, or when new architectural patterns are discovered.
memory-management
Guide for managing Claude Code memory effectively. Use when setting up project memory, optimizing CLAUDE.md files, configuring rules directories, or establishing cross-session knowledge patterns. Covers memory hierarchy, best practices, and context optimization.
memory
Manages memory, SSOT files, and Plans.md operations. Use when user mentions メモリ, memory, SSOT, decisions.md, patterns.md, マージ, merge, Plans.md, 移行, migrate. Do NOT load for: 実装作業, レビュー, 一時的なメモ, セッション中の作業記録.
memory-conventions
This skill should be used when persisting context between sessions, saving project state, loading previous session context, or managing longitudinal memory beyond beads issue tracking.
memory-capture
Capture and organize memories, decisions, and learnings to a memories.md file. Use when you want to save context for future sessions.
memory-bank
Persistent project documentation system that maintains context across sessions. Creates structured Memory Bank files to preserve project knowledge, decisions, and progress.
context-memory
Advanced context and memory management system for AI agents. Provides persistent memory across sessions through daily logs (memory/YYYY-MM-DD.md), long-term curated memory (MEMORY.md), conversation archives with semantic search, and automatic behavioral learning from user satisfaction tracking. Use when you need to: (1) Remember information across sessions, (2) Archive conversations before context loss, (3) Search past discussions, (4) Track and learn from user satisfaction patterns, (5) Maintain session continuity, (6) Implement proactive memory maintenance. Includes conversation-archiver.py and satisfaction-tracker.py scripts, session startup routines, and periodic reflection workflows.
ac-memory-manager
Manage persistent memory for autonomous coding. Use when storing/retrieving knowledge, managing Graphiti integration, persisting learnings, or accessing episodic memory.
atuin-memory
Check, store, and retrieve project memories from atuin kv. Use when starting work on a project, recalling previous context, storing plans or specs, or when the user mentions memory, atuin, or project context.