Common problems and how to fix them.
pip install quilmem failsMake sure you’re on Python 3.11+:
python --version
If you’re in a venv, make sure it’s activated. If you’re on Windows with multiple Pythons, try py -3.11 -m pip install quilmem.
agentmem command not found after installThe agentmem script may not be on your PATH. Try running it as a module:
python -m agentmem --help
If that works, your install is fine but the scripts directory isn’t on PATH. Fix it or use python -m agentmem as the command in MCP configs.
pip install quilmem[mcp]
agentmem init --tool claude --project myapp
.claude/settings.json or ~/.claude/settings.json.cursor/mcp.json or ~/.cursor/mcp.json.windsurf/mcp.json.codex/config.tomlRestart your coding agent. MCP config changes don’t take effect until restart.
agentmem serve
If this prints an error, that’s your problem. If it hangs silently, the server is working (it waits for MCP clients on stdin).
agentmem serve fails with ImportErrorYou need the MCP extra:
pip install quilmem[mcp]
Run doctor and check:
agentmem doctor
The most common cause is the DB path in your MCP config not matching where you ran init. Use absolute paths in the config.
Run init first:
agentmem init --project myapp
agentmem health
agentmem conflicts
agentmem stale --days 14
Fix conflicts by deprecating or superseding the wrong one. Review stale memories and update or deprecate them.
agentmem debug-info
This prints your version, platform, DB state, and health in one block. Paste it into a bug report.
Open an issue with your debug info:
https://github.com/thezenmonster/agentmem/issues/new/choose
Pick the template that fits:
We read every issue. If it broke for you, it’s probably breaking for others.