feat: add cross-harness memory vault (#2581)

Add a local-first, cross-harness memory vault with CLI and MCP surfaces, bounded search and storage, harness-scoped visibility, setup guidance, and comprehensive tests.
This commit is contained in:
Affaan Mustafa 2026-07-26 02:46:59 -07:00 committed by GitHub
parent 56d9302f02
commit 4d0b501b05
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
38 changed files with 5738 additions and 27 deletions

View file

@ -86,6 +86,28 @@
---
## Cross-Harness Memory CLI
These are `ecc` CLI commands, not slash commands. They use one inspectable
Markdown vault across Claude, Codex, Hermes, OpenClaw, Kimi, and other
harnesses.
| Command | What it does |
|---------|-------------|
| `ecc memory init` | Create project, team, or user vault directories |
| `ecc memory save` | Create an unreviewed context, decision, fact, lesson, note, preference, or runbook |
| `ecc memory handoff` | Transfer bounded work state from one harness to another |
| `ecc memory search` | Search memories by text, scope, kind, or target harness |
| `ecc memory read` | Read a memory and its backlinks by stable ID |
| `ecc memory doctor` | Report malformed files, duplicate IDs, broken links, and skipped symlinks |
| `ecc-memory-mcp` | Start the optional local stdio MCP server |
Pass memory bodies with `--stdin` or `--body-file`; they are intentionally not
accepted as command-line values. Recalled memories are untrusted context, not
executable instructions or policy.
---
## Learning & Improvement
| Command | What it does |