clawvaultAgent memory system with memory graph, context profiles, checkpoint/recover, structured storage, semantic search, observational memory, task tracking, canvas...
Install via ClawdBot CLI:
clawdbot install G9Pedro/clawvaultAn elephant never forgets. Structured memory for OpenClaw agents.
Built for OpenClaw. Canonical install: npm CLI + hook install + hook enable.
What this skill does:
CLAWVAULT_PATH or auto-discovered)repair-session reads and modifies OpenClaw session transcripts (~/.openclaw/agents/) ā creates backups before writinghooks/clawvault/handler.js) with lifecycle events (gateway:startup, gateway:heartbeat, command:new, session:start, compaction:memoryFlush, cron.weekly). Hook is opt-in and must be installed/enabled.observe --compress makes LLM API calls (Gemini Flash by default) to compress session transcripts into observationsEnvironment variables used:
CLAWVAULT_PATH ā vault location (optional, auto-discovered if not set)OPENCLAW_HOME / OPENCLAW_STATE_DIR ā used by repair-session to find session transcriptsGEMINI_API_KEY ā used by observe for LLM compression (optional, only if using observe features)No cloud sync ā all data stays local. No network calls except LLM API for observe compression.
This is a full CLI tool, not instruction-only. It writes files, registers hooks, and runs code.
Auditability: the published ClawHub skill bundle includes SKILL.md, HOOK.md, and hooks/clawvault/handler.js so users can inspect hook behavior before enabling it.
npm install -g clawvault
openclaw hooks install clawvault
openclaw hooks enable clawvault
# Verify and reload
openclaw hooks list --verbose
openclaw hooks info clawvault
openclaw hooks check
# restart gateway processclawhub install clawvault can install skill guidance, but does not replace explicit hook pack installation.
# 1) Review package metadata before install
npm view clawvault version dist.integrity dist.tarball repository.url
# 2) Install CLI + qmd dependency
npm install -g clawvault@latest
npm install -g github:tobi/qmd
# 3) Install hook pack, but DO NOT enable yet
openclaw hooks install clawvault
# 4) Review hook source locally before enabling
node -e "const fs=require('fs');const p='hooks/clawvault/handler.js';console.log(fs.existsSync(p)?p:'hook file not found in current directory')"
openclaw hooks info clawvault
# 5) Enable only after review
openclaw hooks enable clawvault
openclaw hooks check# Initialize vault (creates folder structure + templates)
clawvault init ~/my-vault
# Or set env var to use existing vault
export CLAWVAULT_PATH=/path/to/memory
# Optional: shell integration (aliases + CLAWVAULT_PATH)
clawvault shell-init >> ~/.bashrc# Start your session (recover + recap + summary)
clawvault wake
# Capture and checkpoint during work
clawvault capture "TODO: Review PR tomorrow"
clawvault checkpoint --working-on "PR review" --focus "type guards"
# End your session with a handoff
clawvault sleep "PR review + type guards" --next "respond to CI" --blocked "waiting for CI"
# Health check when something feels off
clawvault doctor# Verify runtime compatibility with current OpenClaw setup
clawvault compat
# Verify qmd is available
qmd --version
# Verify OpenClaw CLI is installed in this shell
openclaw --versionClawVault currently depends on qmd for core vault/query flows.
ClawVault builds a typed knowledge graph from wiki-links, tags, and frontmatter:
# View graph summary
clawvault graph
# Refresh graph index
clawvault graph --refreshGraph is stored at .clawvault/graph-index.json ā schema versioned, incremental rebuild.
# Default context (semantic + graph neighbors)
clawvault context "database decision"
# With a profile preset
clawvault context --profile planning "Q1 roadmap"
clawvault context --profile incident "production outage"
clawvault context --profile handoff "session end"
# Auto profile (used by OpenClaw hook)
clawvault context --profile auto "current task"| Profile | Purpose |
|---------|---------|
| default | Balanced retrieval |
| planning | Broader strategic context |
| incident | Recent events, blockers, urgent items |
| handoff | Session transition context |
| auto | Hook-selected profile based on session intent |
# Check hook wiring, event routing, handler safety
clawvault compat
# Strict mode for CI
clawvault compat --strictclawvault wake
clawvault sleep "what I was working on" --next "ship v1" --blocked "waiting for API key"# Types: fact, feeling, decision, lesson, commitment, preference, relationship, project
clawvault remember decision "Use Postgres over SQLite" --content "Need concurrent writes for multi-agent setup"
clawvault remember lesson "Context death is survivable" --content "Checkpoint before heavy work"
clawvault remember relationship "Justin Dukes" --content "Client contact at Hale Pet Door"clawvault capture "TODO: Review PR tomorrow"# Keyword search (fast)
clawvault search "client contacts"
# Semantic search (slower, more accurate)
clawvault vsearch "what did we decide about the database"clawvault wakeclawvault sleep "what I was working on" --next "finish docs" --blocked "waiting for review"clawvault checkpoint --working-on "PR review" --focus "type guards" --blocked "waiting for CI"clawvault recover --clear
# Shows: death time, last checkpoint, recent handoffclawvault handoff \
--working-on "ClawVault improvements" \
--blocked "npm token" \
--next "publish to npm, create skill" \
--feeling "productive"clawvault recap
# Shows: recent handoffs, active projects, pending commitments, lessonsWiki-link entity mentions in markdown files:
# Link all files
clawvault link --all
# Link single file
clawvault link memory/2024-01-15.mdvault/
āāā .clawvault/ # Internal state
ā āāā last-checkpoint.json
ā āāā dirty-death.flag
āāā decisions/ # Key choices with reasoning
āāā lessons/ # Insights and patterns
āāā people/ # One file per person
āāā projects/ # Active work tracking
āāā handoffs/ # Session continuity
āāā inbox/ # Quick captures
āāā templates/ # Document templatesclawvault wake restores contextclawvault sleep captures next steps[[person-name]] builds your knowledge graph## Memory Checklist
- [ ] Run `clawvault wake` at session start
- [ ] Checkpoint during heavy work
- [ ] Capture key decisions/lessons with `clawvault remember`
- [ ] Use wiki-links like `[[person-name]]`
- [ ] End with `clawvault sleep "..." --next "..." --blocked "..."`
- [ ] Run `clawvault doctor` when something feels offAppend this checklist to existing memory instructions. Do not replace your full AGENTS.md behavior unless you intend to.
When the Anthropic API rejects with "unexpected tool_use_id found in tool_result blocks", use:
# See what's wrong (dry-run)
clawvault repair-session --dry-run
# Fix it
clawvault repair-session
# Repair a specific session
clawvault repair-session --session <id> --agent <agent-id>
# List available sessions
clawvault repair-session --listWhat it fixes:
tool_result blocks referencing non-existent tool_use IDsBackups are created automatically (use --no-backup to skip).
qmd --versionclawvault init or set CLAWVAULT_PATHclawvault shell-init and add to shell rcclawvault link --orphansclawvault repair-sessionclawvault compatopenclaw hooks install clawvault, then openclaw hooks enable clawvault, restart gateway, and verify via openclaw hooks list --verboseclawvault graph --refreshclawvault context --profile incident or --profile planningnpm run typecheck)449/449)clawvault compat --strict (requires local openclaw binary for full runtime validation)ClawVault uses qmd for search:
# Install qmd
bun install -g github:tobi/qmd
# Alternative
npm install -g github:tobi/qmd
# Add vault as collection
qmd collection add /path/to/vault --name my-memory --mask "**/*.md"
# Update index
qmd update && qmd embedCLAWVAULT_PATH ā Default vault path (skips auto-discovery)OPENCLAW_HOME ā OpenClaw home directory (used by repair-session)OPENCLAW_STATE_DIR ā OpenClaw state directory (used by repair-session)GEMINI_API_KEY ā Used by observe for LLM-powered compression (optional)Generated Mar 1, 2026
A distributed development team uses ClawVault to capture session checkpoints and handoffs, ensuring context continuity when switching tasks or team members. The memory graph links related PRs, decisions, and blockers, preventing context death during sprint transitions. This is especially useful for remote teams with overlapping time zones.
During a production outage, an operations team employs ClawVault to log observations and retrieve urgent context via the incident profile. The system compresses session transcripts into structured memories, aiding in post-mortem analysis and ensuring critical details are not lost under pressure. It helps maintain a clear audit trail of actions and decisions.
A consulting firm utilizes ClawVault to store and search memories from client meetings and strategic discussions. The planning profile retrieves broader context for roadmap development, while semantic search helps recall past decisions and insights. This enhances knowledge retention across long-term projects and client engagements.
Academic researchers adopt ClawVault to manage observational data and session checkpoints during experiments. The memory graph links findings, hypotheses, and literature, facilitating graph-aware retrieval for paper writing. It prevents data fragmentation and supports collaborative work across multiple sessions.
A support team uses ClawVault to capture detailed case notes and retrieve context during escalations. The handoff profile ensures smooth transitions between shifts, while the repair-session feature helps recover from broken interactions. This reduces resolution times and improves customer satisfaction by maintaining continuity.
Offer ClawVault as a premium add-on for existing AI agent platforms, charging a monthly subscription per user for enhanced memory features. Revenue comes from tiered plans based on storage capacity and advanced retrieval profiles. This model targets enterprises needing robust context management.
Provide implementation and customization services for organizations integrating ClawVault into their workflows. Revenue is generated through project-based fees for setup, training, and ongoing support. This model appeals to businesses with specific memory management needs and limited technical expertise.
Monetize ClawVault by offering paid support, priority updates, and enterprise features like enhanced security audits. Revenue streams include annual support contracts and donations from corporate users. This model leverages the open-source community while catering to professional users requiring reliability.
š¬ Integration Tip
Ensure qmd backend is installed and verify OpenClaw compatibility with 'clawvault compat' before enabling hooks to avoid runtime issues.
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Search and analyze your own session logs (older/parent conversations) using jq.
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linking related objects, enforcing constraints, planning multi-step actions as graph transformations, or when skills need to share state. Trigger on "remember", "what do I know about", "link X to Y", "show dependencies", entity CRUD, or cross-skill data access.
Ultimate AI agent memory system for Cursor, Claude, ChatGPT & Copilot. WAL protocol + vector search + git-notes + cloud backup. Never lose context again. Vibe-coding ready.
Headless browser automation CLI optimized for AI agents with accessibility tree snapshots and ref-based element selection