diff --git a/README.md b/README.md index 0ff9f94..027c2b8 100644 --- a/README.md +++ b/README.md @@ -12,9 +12,9 @@
+ Quick Start •
Why •
Agents •
- Quick Start •
How It Works •
Search •
Memory Evolution •
@@ -26,6 +26,18 @@
---
+Every AI coding agent has the same blind spot. Session ends, memory vanishes. You re-explain architecture. You re-discover bugs. You re-teach preferences. Built-in memory files like CLAUDE.md and .cursorrules are 200-line sticky notes that overflow and go stale. agentmemory replaces that with a searchable, versioned, cross-agent database — 38 MCP tools, triple-stream retrieval (BM25 + vector + knowledge graph), 4-tier memory consolidation, provenance-tracked citations, and cascading staleness so retired facts never pollute your context again. One instance serves Claude Code, Cursor, Codex, Windsurf, and any MCP client simultaneously. 573 tests. Zero external DB dependencies.
+
+The result is measurable. On 240 real observations across 30 sessions, agentmemory hits 64% Recall@10 and perfect MRR while using 92% fewer tokens than dumping everything into context. When an agent searches "database performance optimization," it finds the N+1 fix you made three weeks ago — something keyword grep literally cannot do. Memories version automatically, supersede each other, propagate staleness to related graph nodes, and sync across agent instances via P2P mesh. Your agents stop repeating mistakes. Your context stays clean. Your sessions start fast.
+
+```bash
+git clone https://github.com/rohitg00/agentmemory.git && cd agentmemory
+docker compose up -d && npm install && npm run build && npm start
+curl http://localhost:3111/agentmemory/health
+```
+
+---
+
## Why agentmemory
AI coding agents forget everything between sessions. You explain the same architecture, re-discover the same patterns, and re-learn the same preferences every time. agentmemory fixes that.
@@ -61,6 +73,8 @@ No manual notes. No copy-pasting. The agent just *knows*.
| **Self-healing** | Circuit breaker, provider fallback chain, self-correcting LLM output, health monitoring |
| **Claude Code bridge** | Bi-directional sync with `~/.claude/projects/*/memory/MEMORY.md` |
| **Cross-agent MCP** | Standalone MCP server for Cursor, Codex, Gemini CLI, Windsurf, any MCP client |
+| **Citation provenance** | JIT verification traces any memory back to source observations and sessions |
+| **Cascading staleness** | Superseded memories auto-flag related graph nodes, edges, and siblings as stale |
| **Knowledge graph** | Entity extraction + BFS traversal across files, functions, concepts, errors |
| **4-tier memory** | Working → episodic → semantic → procedural consolidation with strength decay |
| **Team memory** | Namespaced shared + private memory across team members |
@@ -83,6 +97,8 @@ agentmemory is the searchable database behind the sticky notes.
| Cross-session recall | Only within line cap | Full corpus search |
| Cross-agent | Per-agent files (no sharing) | MCP + REST API (any agent) |
| Multi-agent coordination | Impossible | Leases, signals, actions, routines |
+| Cross-agent sync | No | P2P mesh (7 scopes: memories, actions, semantic, procedural, relations, graph) |
+| Memory trust | No verification | Citation chain back to source observations with confidence scores |
| Semantic search | No (keyword grep) | Yes (Recall@10: 64% vs 56% for grep) |
| Memory lifecycle | Manual pruning | Ebbinghaus decay + tiered eviction |
| Knowledge graph | No | Entity extraction + temporal versioning |
@@ -117,7 +133,7 @@ These agents support hooks natively. agentmemory captures tool usage automatical
### MCP support (any MCP-compatible agent)
-Any agent that connects to MCP servers can use agentmemory's 37 tools, 6 resources, and 3 prompts. The agent actively queries and saves memory through MCP calls.
+Any agent that connects to MCP servers can use agentmemory's 38 tools, 6 resources, and 3 prompts. The agent actively queries and saves memory through MCP calls.
| Agent | How to connect |
|---|---|
@@ -146,7 +162,7 @@ GET /agentmemory/profile # Get project intelligence
|---|---|
| Claude Code user | Plugin install (hooks + MCP + skills) |
| Building a custom agent with Claude SDK | AgentSDKProvider (zero config) |
-| Using Cursor, Windsurf, or any MCP client | MCP server (37 tools + 6 resources + 3 prompts) |
+| Using Cursor, Windsurf, or any MCP client | MCP server (38 tools + 6 resources + 3 prompts) |
| Building your own agent framework | REST API (93 endpoints) |
| Sharing memory across multiple agents | All agents point to the same iii-engine instance |
@@ -184,7 +200,7 @@ open http://localhost:3113
{
"status": "healthy",
"service": "agentmemory",
- "version": "0.6.0",
+ "version": "0.6.1",
"health": {
"memory": { "heapUsed": 42000000, "heapTotal": 67000000 },
"cpu": { "percent": 2.1 },
@@ -405,7 +421,7 @@ Collects every 30 seconds: heap usage, CPU percentage (delta sampling), event lo
## MCP Server
-### Tools (37)
+### Tools (38)
| Tool | Description |
|------|-------------|
@@ -446,6 +462,7 @@ Collects every 30 seconds: heap usage, CPU percentage (delta sampling), event lo
| `memory_heal` | Auto-fix stuck, orphaned, and inconsistent state |
| `memory_facet_tag` | Attach structured dimension:value tags to targets |
| `memory_facet_query` | Query targets by facet tags with AND/OR logic |
+| `memory_verify` | Trace a memory's provenance back to source observations and sessions |
### Resources (6)
@@ -603,7 +620,7 @@ ANTHROPIC_API_KEY=sk-ant-...
## API
-93 endpoints on port `3111` (87 core + 6 MCP protocol). Protected endpoints require `Authorization: Bearer