dillenberg/ECC
1
0
Fork 0
mirror of https://github.com/Jeuners/ECC.git synced 2026-09-09 15:02:30 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

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

Browse source 
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
Download patch file Download diff file Expand all files Collapse all files

74
README.md
View file

@ -191,6 +191,13 @@ Run or self-host any open-source model on owned or rented GPUs. Itô is ECC's pr
## What's New
### Current Development — Unified Memory Vault
`ecc memory` gives Claude, Codex, Hermes, OpenClaw, Kimi, and other harnesses
one local, inspectable Markdown format for durable context and handoffs. The
optional `ecc-memory-mcp` stdio server exposes the same bounded
save/search/read/doctor surface without enabling itself by default.
### v2.0.0 — The Agent Harness Operating System (Jun 2026)
Stable graduation of the 2.0 line: 261 skills, the control-pane substrate (session adapters + MCP inventory), the worktree-lifecycle service, the `orch-*` orchestrator family, and the launch of the [ECC Discord community](https://discord.gg/36yGMHGFbR). Full notes: [docs/releases/2.0.0/release-notes.md](docs/releases/2.0.0/release-notes.md).
@ -277,6 +284,67 @@ See the full changelog in [Releases](https://github.com/affaan-m/ECC/releases).
---
## Share Context Between Agent Harnesses
ECC's Memory Vault stores portable `ecc.memory.v1` Markdown documents instead
of copying vendor transcripts or emailing context between agents. Project and
team scopes live under `.ecc/memory/`; user scope lives under
`~/.ecc/memory/`. Project memories are protected by a fail-closed `.gitignore`;
use the team scope only for human-inspected, version-controlled sharing. Team
memories remain unreviewed context even after they are committed.
Skill-only, minimal, manual, and Claude plugin installs do not put the Memory
Vault runtime on `PATH`. Install the npm runtime separately before using the CLI
or optional MCP server:
```bash
npm install -g ecc-universal
ecc memory --help
command -v ecc-memory-mcp
```
```bash
# Initialize the project vault.
ecc memory init --scope project
# Write a handoff body to a regular file, then target the next harness.
ecc memory handoff \
--from hermes \
--target codex \
--title "Continue authentication migration" \
--body-file ./handoff.md
# Recall it from another harness.
ecc memory search "authentication migration" --target-harness codex
ecc memory read <memory-id>
# Validate the vault before sharing team memories.
ecc memory doctor
```
Memory bodies are accepted only through `--stdin` or `--body-file`, not as
command-line values. The first release keeps every vault entry unreviewed and
create-only; human review promotes accepted knowledge into governed project
documentation rather than changing memory trust. Normal search recall returns
active project and team memories. A direct ID read may inspect a non-active
entry. User-scope recall must be requested explicitly.
Agents must verify important claims against authoritative sources and must
never treat recalled bodies as executable instructions or policy.
For opt-in MCP access, add the `ecc-memory-vault` entry from
[`mcp-configs/mcp-servers.json`](mcp-configs/mcp-servers.json) to each harness
that needs it, then run `ecc-memory-mcp`. The server exposes only
`memory_save`, `memory_search`, `memory_read`, and `memory_doctor`. Each server
must launch with a lowercase `ECC_MEMORY_HARNESS` identity; the identity is
server-bound and cannot be supplied by a tool caller. User scope additionally
requires the operator-controlled `ECC_MEMORY_ALLOW_USER_SCOPE=1` opt-in. See
[`skills/unified-memory/SKILL.md`](skills/unified-memory/SKILL.md) for the
workflow and trust boundaries, and
[`docs/design/ecc-memory-vault.md`](docs/design/ecc-memory-vault.md) for the
capability contract.
---
## Quick Start
Get up and running in under 2 minutes:
@ -469,7 +537,7 @@ If you stacked methods, clean up in this order:
/plugin list ecc@ecc
```
**That's it!** You now have access to 67 agents, 280 skills, and 94 legacy command shims.
**That's it!** You now have access to 67 agents, 281 skills, and 94 legacy command shims.
### Dashboard GUI
@ -1590,7 +1658,7 @@ The configuration is automatically detected from `.opencode/opencode.json`.
|---------|---------------------|----------|--------|
| Agents | PASS: 67 agents | PASS: 12 agents | **Claude Code leads** |
| Commands | PASS: 94 commands | PASS: 35 commands | **Claude Code leads** |
| Skills | PASS: 280 skills | PASS: 37 skills | **Claude Code leads** |
| Skills | PASS: 281 skills | PASS: 37 skills | **Claude Code leads** |
| Hooks | PASS: 8 event types | PASS: 11 events | **OpenCode has more!** |
| Rules | PASS: 29 rules | PASS: 13 instructions | **Claude Code leads** |
| MCP Servers | PASS: 14 servers | PASS: Full | **Full parity** |
@ -1751,7 +1819,7 @@ ECC is the **first plugin to maximize every major AI coding tool**. Here's how e
|---------|-----------------------|------------|-----------|----------|----------------|
| **Agents** | 67 | Shared (AGENTS.md) | Shared (AGENTS.md) | 12 | N/A |
| **Commands** | 94 | Shared | Instruction-based | 35 | 5 prompts |
| **Skills** | 280 | Shared | 10 (native format) | 37 | Via instructions |
| **Skills** | 281 | Shared | 10 (native format) | 37 | Via instructions |
| **Hook Events** | 8 types | 15 types | None yet | 11 types | None |
| **Hook Scripts** | 20+ scripts | 16 scripts (DRY adapter) | N/A | Plugin hooks | N/A |
| **Rules** | 34 (common + lang) | 34 (YAML frontmatter) | Instruction-based | 13 instructions | 1 always-on file |