agent-shared-memory

Manage an append-only shared memory ledger in .coord/memory.yml across multi-agent runs.

23|5|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/WenyuChiou/agent-collab-skills --skill agent-shared-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-shared-memory
Source: https://github.com/WenyuChiou/agent-collab-skills/tree/main/skills/agent-shared-memory
Command: npx skills add https://github.com/WenyuChiou/agent-collab-skills --skill agent-shared-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The persistent blackboard between Claude session A, Codex session B, and Gemini session C — none of which see each other's conversation history natively. memory.yml is append-only and stores decisions, open questions, artifacts, and agent sessions across multi-agent runs to provide continuity.

Core Features & Use Cases

  • Append-only memory.yml file that records decisions, open questions, artifacts, and agent history as the project runs.
  • Read mode generates a digest of current state; append mode logs new entries atomically and safely.
  • Initialize memory per project and maintain a per-session memory context across agent runs.

Quick Start

Initialize multi-agent shared memory for your project and start logging the first decisions.

Frequently Asked Questions about agent-shared-memory

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

FAQPage Schema
How do I share memory and decisions across multiple AI agents like Claude, Codex, and Gemini?

To share memory across multiple AI agents, use a persistent, append-only shared memory ledger like memory.yml. It records decisions, open questions, and agent history, providing continuity between independent Claude, Codex, and Gemini sessions that lack shared conversation history.

What is an append-only audit trail for multi-agent coordination?

An append-only audit trail for multi-agent coordination is a persistent ledger that logs decisions, open questions, and artifacts sequentially. It ensures project continuity by recording agent history across multiple runs without modifying past entries.

How do I initialize a shared memory ledger for a multi-agent project?

To initialize shared memory for a multi-agent project, create a per-project scoping directory named .coord. The system generates a memory.yml file inside this directory to start logging decisions and artifacts.

Can I safely append new decisions to memory.yml while multiple agents are running?

Yes, you can safely append new decisions to memory.yml while multiple agents are running. The system uses atomic writes secured with a lock to prevent data corruption when logging entries across concurrent multi-agent sessions.

How do I generate a digest of the current project state from multi-agent memory?

To generate a digest of the current project state from multi-agent memory, use the read mode. This function processes the append-only memory.yml ledger and summarizes existing decisions, open questions, artifacts, and agent history.

When do I need a persistent blackboard for multi-agent workflows?

You need a persistent blackboard for multi-agent workflows when coordinating separate AI sessions on a single project. It bridges the gap when agents like Claude, Codex, and Gemini cannot natively access each other's conversation histories.