From 61f2d3436676e4f854cf0c7a42bbdf77e3d16ccd Mon Sep 17 00:00:00 2001 From: dtzp555 Date: Sun, 15 Mar 2026 14:18:06 +1000 Subject: [PATCH] docs: add "Why this plugin?" section highlighting differentiators Emphasize zero-dependency, plain-file, backup/migrate simplicity, upgrade-proof design vs vector-DB-based memory plugins. Co-Authored-By: Claude Opus 4.6 --- README.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/README.md b/README.md index b8feb52..0d4f718 100644 --- a/README.md +++ b/README.md @@ -4,6 +4,20 @@ OpenClaw **lifecycle plugin** for short-term working continuity. Preserves structured in-flight work state across `/new`, reset, gateway restarts, model fallback, and context compaction. +## Why this plugin? + +There are feature-rich memory plugins out there (vector search, semantic dedup, smart extraction). We took a different path: + +- **Zero dependency** — no embedding API, no vector DB, no external services +- **Plain files** — data is markdown, human-readable, editable, greppable +- **Hook-driven** — doesn't rely on model behavior, works with any model +- **Backup = copy** — `cp` / `scp` / `rsync` is your entire backup strategy +- **Migrate in seconds** — copy files to new host, done. No re-indexing, no model binding +- **Upgrade-proof** — doesn't occupy the `contextEngine` slot, doesn't depend on OpenClaw internals +- **Native-consistent** — aligns with OpenClaw's `memory/` file conventions + +If what you need is "don't lose work across sessions" rather than "semantic search over 100k memories", this plugin is for you. + ## What problem does this solve? OpenClaw already preserves transcripts, compaction summaries, memory files, and session memory search. But those don't always answer the most operational question: