I built an open-source persistent memory layer for AI coding agents
Summary
An open-source persistent memory layer for AI coding agents that stores and retrieves project decisions and context using Postgres and pgvector, aiming to reduce context window size and improve agent consistency.
Similar Articles
I got tired of re-explaining my project to every AI tool, so I built a local memory layer for them
The author built mem-port, a local MCP server that gives AI copilots (ChatGPT, Claude Code, Cursor, Windsurf) shared long-term memory via embedded SurrealDB, solving context drift between AI tools.
rohitg00/agentmemory
agentmemory is an open-source persistent memory layer for AI coding agents (Claude Code, Cursor, Gemini CLI, Codex CLI, etc.) that uses knowledge graphs, confidence scoring, and hybrid search to give agents long-term memory across sessions via MCP, hooks, or REST API. Built on the iii engine, it requires no external databases and exposes 51 MCP tools.
PROJECTMEM: A Local-First, Event-Sourced Memory and Judgment Layer for AI Coding Agents
PROJECTMEM is an open-source, local-first memory and judgment layer for AI coding agents that records development events and provides deterministic warnings before repeating failed actions, reducing token waste and improving reproducibility.
I built a self-hosted memory layer that works across Claude, ChatGPT, and Cursor
The author introduces an open-source MCP server running on Cloudflare Workers that provides persistent, searchable memory for AI clients like Claude, ChatGPT, and Cursor using vector embeddings and duplicate detection.
How are you handling memory across your agents' sessions?
A developer discussion post asking how others handle persistent memory across AI agent sessions, comparing approaches like notes files, vector DBs, mem0, Zep, and Letta, and raising concerns about stale or outdated facts causing agents to act on obsolete decisions.