cass-memory-system - shared memory across agents
Procedural memory layer that turns scattered Claude Code, Codex, and Cursor session transcripts into persistent, cross-agent memory. Every agent learns from every other agent's prior work.
This entry doesn't have a long-form writeup yet. Follow the source link above for the full context.
Featured in
Claude Code tools, plugins, and integrations
The best tools, MCP servers, and harnesses for getting more out of Claude Code - orchestration, observability, telemetry, and remote control.
Multi-agent frameworks and orchestration
Frameworks, harnesses, and DSLs for coordinating multiple AI agents across handoffs, parallel waves, and tool use.
Memory and knowledge graphs for AI agents
Memory layers, knowledge graphs, and persistent context stores for agents - the substrate underneath useful long-running systems.
Related entries
Egregore - shared memory for multiplayer Claude Code
Local MIT substrate that gives a team of Claude Code sessions a shared memory and coordination layer, spun up via npx create-egregore.
pro-workflow - self-correcting Claude Code memory
Claude Code workflow where corrections persist as compounding memory across 50+ sessions, with parallel worktrees, agent teams, and 17 prebuilt skills.
wanman - worktree-isolated multi-agent runtime for Claude Code and Codex
Multi-agent runtime that spawns each Claude Code or Codex agent in its own git worktree and home directory. JSON-RPC subprocess control, task pooling, artifact storage. Solves the share-a-directory failure mode that breaks most multi-agent harnesses.
mex - persistent project memory for AI agents
Structured scaffold and drift-detection CLI that gives Claude Code, Cursor, and other coding agents a project-level memory file that stays in sync with the codebase.