note.md + OpenClaw

Why this pairing works

OpenClaw keeps its memory as plain markdown — MEMORY.md for long-term facts, memory/YYYY-MM-DD.md for daily working notes. That's structurally identical to a note.md vault's wikipage/ and dailynote/ convention: dated outlines plus curated pages. Same idea, convergently evolved.

Pair them and each side gets what it lacks: OpenClaw gets a human who actually reads and curates its memory in a view built for that; you get an agent that works around the clock and writes everything down where you can see it.

Setup

1. Put an AGENTS.md at your vault root describing the conventions (sidecar pairing, daily-note paths, [[yyyy-MM-dd]] date links). Grab the summary from llms-full.txt.
2. Point OpenClaw's workspace at your vault (or symlink its memory/ into dailynote/ — dated files are dated files).
3. Have OpenClaw write reports and research as .md documents into the vault.
4. Open them in note.md, read, highlight, question — your marks land in sidecar .note.md files.
5. Tell OpenClaw to read sidecars before follow-up work. Your judgment becomes its steering signal.

The loop in practice

Evening: OpenClaw researches a topic and drops research/topic.md in the vault. Morning: you read it in note.md over coffee, highlight two claims, add a doubt. Afternoon: OpenClaw picks up research/topic.note.md, sees exactly which claims earned your attention, and digs where you doubted. No prompt engineering — just files.

FAQ

Does OpenClaw need a plugin to work with note.md?

No. Both sides speak plain markdown files. An AGENTS.md at the vault root describing the conventions is all the 'integration' there is.

Is it safe to let OpenClaw write into my vault?

Keep the vault in git (see the GitHub guide) so every agent write is diffable and revertible. By convention agents should not write into your .note.md sidecars — state that rule in AGENTS.md.