Skip to content

Awesome list for AI agent harness engineering: tools, patterns, evals, memory, MCP, permissions, observability, and orchestration.

Add claude-memory-compiler: trace-driven memory evolution for coding agents

ai-boost243d708f5278
diff --git a/README.md b/README.md
index e653d6b..7d2d97d 100644
--- a/README.md
+++ b/README.md
@@ -212,6 +212,7 @@ Harness components organized by the problem they solve, not by vendor.
- [engram](https://github.com/Gentleman-Programming/engram) — Persistent memory for AI coding agents delivered as a single Go binary with SQLite + FTS5 and 18 MCP tools for save, search, session lifecycle, and conflict detection. The agent-agnostic, zero-dependency design makes cross-session memory a local harness primitive rather than a managed cloud service. ![Stars](https://img.shields.io/github/stars/Gentleman-Programming/engram?style=flat-square&label=★&color=yellow)
- [MemPalace](https://github.com/MemPalace/mempalace) — Local-first AI memory system that stores conversation history verbatim and retrieves it with semantic search through a structured palace architecture (wings, rooms, drawers). Achieves 96.6% R@5 on LongMemEval with zero LLM calls, making it the best-benchmarked open-source memory layer for agents that need cross-session persistence without cloud dependencies. ![Stars](https://img.shields.io/github/stars/MemPalace/mempalace?style=flat-square&label=★&color=yellow)
- [agentmemory](https://github.com/rohitg00/agentmemory) — Persistent memory layer purpose-built for coding agents with 95.2% retrieval accuracy and 92% token reduction, backed by real-world benchmarks. Its cross-agent architecture — one memory server serving Claude Code, Cursor, Codex, and OpenCode through MCP and hooks — makes cross-session memory a portable harness primitive rather than a vendor-specific add-on. ![Stars](https://img.shields.io/github/stars/rohitg00/agentmemory?style=flat-square&label=★&color=yellow)
+- [claude-memory-compiler](https://github.com/coleam00/claude-memory-compiler) — Turns raw Claude Code sessions into a self-evolving knowledge base: hooks capture every interaction, the Agent SDK extracts decisions and lessons, and an LLM compiler distills them into structured, cross-referenced articles that improve retrieval quality over time. The most concrete open-source implementation of trace-driven memory evolution for coding agents. ![Stars](https://img.shields.io/github/stars/coleam00/claude-memory-compiler?style=flat-square&label=★&color=yellow)
- [How We Built Agent Builder's Memory System](https://blog.langchain.com/how-we-built-agent-builders-memory-system/) — LangChain's engineering account of a COALA-based three-tier memory system (procedural/semantic/episodic) backed by PostgreSQL but exposed to agents as a virtual filesystem. Key harness decisions: human-in-the-loop approval gates every memory write (blocking prompt-injection via malformed writes), validation errors are fed back to the LLM for self-correction, and AGENTS.md serves as the agent's procedural memory anchor.
- [Building an Agentic Memory System for GitHub Copilot](https://github.blog/ai-and-ml/github-copilot/building-an-agentic-memory-system-for-github-copilot/) — GitHub's January 15, 2026 write-up is one of the clearest public discussions of deployed cross-agent memory: repository-scoped memories are shared across coding agent, CLI, and code review, but only after just-in-time verification against the current code state. The core harness lesson is that memory quality is mostly a freshness and invalidation problem — stale, branch-specific memories are often more dangerous than having no memory at all.
- [MemArchitect: A Policy-Driven Memory Governance Layer](https://arxiv.org/abs/2603.18330) — Proposes a governance layer that decouples memory lifecycle management (decay, conflict resolution, privacy enforcement) from model weights, directly addressing the "zombie memory" problem: outdated facts sitting in the context window that only a harness-level eviction policy — not the model — can remove.