Persistent memory and agent lifecycle for Claude Code — because sessions shouldn't start from zero.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Still active enough to matter. Good candidate for a fast stack test instead of a long evaluation loop.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health 42/100. no security policy. 7 open issues make this testable, but not something to trust blind.
AI Agent
Claude Code
Model
Claude
Fastest way to find out if hmem belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add hmem -- npx hmemRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove hmemNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ hmem ← registers here
Persistent memory and agent lifecycle for Claude Code — because sessions shouldn't start from zero.
Source: GitHub repository
Source check: July 18, 2026
Upstream commit: July 9, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.