home / skills / openclaw / skills / 2026-02-10-clawhub-clawvault-1-5-1

2026-02-10-clawhub-clawvault-1-5-1 skill

/skills/pin-alt/2026-02-10-clawhub-clawvault-1-5-1

This skill helps OpenClaw agents persist and recover memory with structured, searchable vaults, ensuring session continuity and rapid recap.

npx playbooks add skill openclaw/skills --skill 2026-02-10-clawhub-clawvault-1-5-1

Review the files below or copy the command above to add this skill to your agents.

Files (108)
SKILL.md
5.9 KB
---
name: clawvault
version: 1.5.1
description: Structured memory system for OpenClaw agents. Context death resilience (checkpoint/recover), structured storage, Obsidian-compatible markdown, local semantic search, and session transcript repair.
author: Versatly
repository: https://github.com/Versatly/clawvault
---

# ClawVault 🐘

An elephant never forgets. Structured memory for OpenClaw agents.

> **Built for [OpenClaw](https://openclaw.ai)** — install via `clawhub install clawvault`

## Install

```bash
npm install -g clawvault
```

## Setup

```bash
# 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
```

## Quick Start for New Agents

```bash
# 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
```

## Core Commands

### Wake + Sleep (primary)

```bash
clawvault wake
clawvault sleep "what I was working on" --next "ship v1" --blocked "waiting for API key"
```

### Store memories by type

```bash
# 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"
```

### Quick capture to inbox

```bash
clawvault capture "TODO: Review PR tomorrow"
```

### Search (requires qmd installed)

```bash
# Keyword search (fast)
clawvault search "client contacts"

# Semantic search (slower, more accurate)
clawvault vsearch "what did we decide about the database"
```

## Context Death Resilience

### Wake (start of session)

```bash
clawvault wake
```

### Sleep (end of session)

```bash
clawvault sleep "what I was working on" --next "finish docs" --blocked "waiting for review"
```

### Checkpoint (save state frequently)

```bash
clawvault checkpoint --working-on "PR review" --focus "type guards" --blocked "waiting for CI"
```

### Recover (manual check)

```bash
clawvault recover --clear
# Shows: death time, last checkpoint, recent handoff
```

### Handoff (manual session end)

```bash
clawvault handoff \
  --working-on "ClawVault improvements" \
  --blocked "npm token" \
  --next "publish to npm, create skill" \
  --feeling "productive"
```

### Recap (bootstrap new session)

```bash
clawvault recap
# Shows: recent handoffs, active projects, pending commitments, lessons
```

## Auto-linking

Wiki-link entity mentions in markdown files:

```bash
# Link all files
clawvault link --all

# Link single file
clawvault link memory/2024-01-15.md
```

## Folder Structure

```
vault/
├── .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 templates
```

## Best Practices

1. **Wake at session start** — `clawvault wake` restores context
2. **Checkpoint every 10-15 min** during heavy work
3. **Sleep before session end** — `clawvault sleep` captures next steps
4. **Use types** — knowing WHAT you're storing helps WHERE to put it
5. **Wiki-link liberally** — `[[person-name]]` builds your knowledge graph

## Checklist for AGENTS.md

```markdown
## 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 off
```

## Session Transcript Repair (v1.5.0+)

When the Anthropic API rejects with "unexpected tool_use_id found in tool_result blocks", use:

```bash
# 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 --list
```

**What it fixes:**
- Orphaned `tool_result` blocks referencing non-existent `tool_use` IDs
- Aborted tool calls with partial JSON
- Broken parent chain references

Backups are created automatically (use `--no-backup` to skip).

## Troubleshooting

- **qmd not installed** — run `bun install -g github:tobi/qmd` or `npm install -g qmd`
- **No ClawVault found** — run `clawvault init` or set `CLAWVAULT_PATH`
- **CLAWVAULT_PATH missing** — run `clawvault shell-init` and add to shell rc
- **Too many orphan links** — run `clawvault link --orphans`
- **Inbox backlog warning** — process or archive inbox items
- **"unexpected tool_use_id" error** — run `clawvault repair-session`

## Integration with qmd

ClawVault uses [qmd](https://github.com/tobi/qmd) for search:

```bash
# Install qmd
bun 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 embed
```

## Environment Variables

- `CLAWVAULT_PATH` — Default vault path (skips auto-discovery)

## Links

- npm: https://www.npmjs.com/package/clawvault
- GitHub: https://github.com/Versatly/clawvault
- Issues: https://github.com/Versatly/clawvault/issues

Overview

This skill provides a structured memory system for OpenClaw agents, focused on context-death resilience, recoverable checkpoints, and semantic local search. It stores agent memories in Obsidian-compatible markdown, supports session transcript repair, and integrates with qmd for fast and semantic search. The tool is designed to make agent sessions resumable, auditable, and easy to link into a lightweight knowledge graph.

How this skill works

ClawVault organizes memories into typed folders (decisions, lessons, people, projects, handoffs, inbox) and keeps internal state for checkpoints and crash detection. Agents interact via CLI commands to wake, checkpoint, capture, sleep, and recover; each command writes markdown files and internal metadata to the vault. It also provides local keyword and semantic search (via qmd) and repair utilities for broken session transcripts and orphaned tool_result references.

When to use it

  • Start every agent session to restore context and recent handoffs (clawvault wake).
  • During long runs or risky operations to save intermediate state (clawvault checkpoint).
  • Before ending a session to capture next steps and blockers (clawvault sleep/hand off).
  • When searchability and local semantic recall are needed for agent decisions.
  • If a session transcript is rejected or corrupted and needs automated repair.

Best practices

  • Run clawvault wake at session start and clawvault sleep at session end to preserve continuity.
  • Checkpoint frequently (every 10–15 minutes) during heavy work or multi-agent exchanges.
  • Use typed remembers (fact, decision, lesson, relationship, project) so entries land in the right folder.
  • Enable wiki-links ([[name]]) to build a lightweight knowledge graph and make linking automatic.
  • Integrate qmd for semantic search and keep the qmd index updated after vault changes.

Example use cases

  • An agent crashes mid-task: recover state from last checkpoint and resume work with clawvault recover.
  • Capture design decisions and reasoning about database choice using clawvault remember decision.
  • Daily agent handoffs: summarize what was worked on, blockers, and next steps with clawvault sleep/hand off.
  • Repair session transcripts that fail model-tool validation using clawvault repair-session.
  • Quickly find relevant people, lessons, or past decisions via keyword or semantic search (clawvault search / vsearch).

FAQ

How do I restore a session after a crash?

Run clawvault wake to load recent handoffs and checkpoints. Use clawvault recover to inspect death time, last checkpoint, and available handoffs.

Can I search the vault semantically?

Yes. Install qmd and add the vault as a collection, then use clawvault vsearch for semantic queries.

What does repair-session fix?

It repairs orphaned tool_result references, partial JSON from aborted tool calls, and broken parent chains; backups are created automatically.