Agent-Memory vs code-session-memory
Persistent memory for AI coding agents compared
Agent-Memory and code-session-memory both capture coding-agent sessions so developers and agents can search past work. Agent-Memory combines several retrieval methods and memory tiers on the iii engine, while code-session-memory centers on OpenAI embeddings and searchable session indexes.
Agent-Memory: Persistent Memory for AI Coding Agents on iii
Agent-Memory adds persistent, searchable memory to coding agents through the iii engine, sharing context across Claude Code, Cursor, Gemini CLI, Codex CLI, and other MCP or HTTP clients. It captures session activity and retrieves relevant context for later work.
code-session-memory: Search AI Coding Sessions with OpenAI Embeddings
code-session-memory indexes sessions from OpenCode, Claude Code, Cursor, VS Code, Codex, and Gemini CLI into shared, searchable memory using OpenAI embeddings. It stores data locally with SQLite and sqlite-vec by default, with PostgreSQL and pgvector as an optional shared backend.
| Agent-Memory | code-session-memory | |
|---|---|---|
| Language | — | TypeScript |
| License | Apache-2.0 | — |
| Stars | 9 | 20 |
| Forks | 4 | 2 |
| Last analyzed | Nov 1, 2026 | Oct 30, 2026 |
Key differences
- Agent-Memory captures prompts, tool activity, and session events, then combines keyword, vector, and graph retrieval; code-session-memory indexes session messages for semantic search using OpenAI embeddings.
- Agent-Memory organizes information into working, episodic, semantic, and procedural memory tiers; code-session-memory provides session browsing, filters, and summaries for restarting work.
- Agent-Memory runs on the iii engine and supports MCP and REST integrations; code-session-memory offers MCP, CLI, and web interfaces, with SQLite and sqlite-vec by default or PostgreSQL and pgvector as an option.
- Agent-Memory requires Node.js 20 or later; code-session-memory requires Node.js 22 or later and an OpenAI API key for indexing and semantic queries.
- Agent-Memory is licensed Apache-2.0; code-session-memory's README states MIT, and the supplied project data advises verifying the license file.
- Both projects have small contributor bases and no releases in the past year; Agent-Memory has had no commits in the past 90 days, while code-session-memory has recent commits.
Choose Agent-Memory if you…
- need persistent, tiered memory with keyword, vector, and graph retrieval.
- want one memory server to share context across MCP or HTTP clients.
- use agent hooks and plugins to capture sessions automatically.
Choose code-session-memory if you…
- want semantic search over sessions using OpenAI embeddings.
- prefer local SQLite storage, with PostgreSQL and pgvector available for multi-machine sharing.
- need session filters, interactive browsing, or structured restart summaries.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.