unified-memory

Share durable context and handoffs between AI agent harnesses through a local memory vault.

Updated May 7, 2026
One-click install
npx skills add https://github.com/mirzadham/trainingroombookingsystem2 --skill unified-memory-mirzadham
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unified-memory
Source: https://github.com/mirzadham/trainingroombookingsystem2/tree/main/.agent/.agents/skills/unified-memory
Command: npx skills add https://github.com/mirzadham/trainingroombookingsystem2 --skill unified-memory-mirzadham

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ecc-universal.

What problem does it solve? AI coding agents like Claude, Codex, Hermes, Cursor, and OpenCode work in isolated sessions with no shared memory, so context, decisions, and task state are lost when switching between harnesses or resuming work later. ## Core Features & Use Cases - Cross-Harness Memory Vault: Save, search, and read portable ecc.memory.v1 Markdown documents shared across all participating agents via the ECC Memory Vault. - Structured Handoffs: Transfer work between agents (e.g., Codex to Claude) with handoff documents capturing objective, evidence, blockers, and next actions. - Scoped Storage & Validation: Organize memories into project, team, and user scopes with fail-closed .gitignore protection, and run ecc memory doctor to diagnose malformed entries, broken links, or duplicate IDs. - Use Case: After finishing a migration investigation in Codex, save a handoff memory so Claude can resume the rollout in a later session with full context on tests run and remaining risks. ## Quick Start Install the ecc-universal npm runtime, then ask the agent to search the memory vault for prior context on your task and save a handoff memory for the next agent.

Frequently Asked Questions about unified-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I share context between Claude and Codex agents?▼

Use the ECC Memory Vault to save context as portable Markdown documents that any participating harness can search and read. Write a handoff with `ecc memory handoff` specifying the source and target harness so the next agent can resume the task.

How do I install the ECC Memory Vault CLI?▼

Install the runtime globally with `npm install -g ecc-universal`, then verify with `ecc memory --help`. The skill itself is only guidance; the CLI and the `ecc-memory-mcp` binary must exist on PATH before use.

What memory scopes does the ECC vault support?▼

The vault supports three scopes: project (repo-local, gitignore-protected), team (version-controlled for human review), and user (operator context across repositories). User scope is never included implicitly and must be requested explicitly with `--scope user`.

Can I store secrets or credentials in the memory vault?▼

No. Never store passwords, tokens, private keys, cookies, or sensitive personal data in the vault. The runtime rejects known secret shapes, but that is only a backstop, not a complete classifier.

Why does ecc memory doctor report errors in my vault?▼

The doctor command detects malformed memories, broken links, duplicate IDs, and skipped symbolic links. It does not delete or rewrite anything, so you must repair the reported files manually before committing team memories.