agentic-stack (.agent/ folder) vs claude-mem
Both in the memory & context category. Side-by-side — pick the one that fits your stack tonight.
One portable folder of memory + skills that works across every AI agent tool.
- rating
- 3★
- tested
- —
- cost
- free
- install
- drop-in
- stars
- 1,357
- updated
- 5d ago
You only use one agent tool and never plan to switch.
Never re-explain your project to Claude again. Auto-memory across sessions.
- rating
- 4★
- tested
- —
- cost
- free
- install
- drop-in
- stars
- 65,382
- updated
- 5d ago
You only use Claude for one-off tasks and don't need it to remember anything later.
why it matters · agentic-stack (.agent/ folder)
Your agent's memory, skills, and workflows usually get locked to whichever tool you started with — Claude Code, Cursor, Windsurf, whatever. Switch tools and you start over from zero. agentic-stack is a simple `.agent/` folder structure that holds everything — memory, skill files, protocols — in one place. Drop it in any project and every major agent tool reads from it. Swap Claude Code for Cursor next month and your lessons come with you.
why it matters · claude-mem
claude-mem watches every Claude Code session — what you asked, what worked, what broke — compresses it all, and drops the relevant bits into your next session automatically. You stop re-explaining your project on day 2. If your agent keeps forgetting context you already gave it, or you switch between projects a lot, this is the fix. Works on any repo, plugin install, free.