Help us improve
Share bugs, ideas, or general feedback.
From claude-mem
Diagnose and fix claude-mem installation issues. Checks PM2 worker status, database integrity, service health, dependencies, and provides automated fixes for common problems.
npx claudepluginhub fabio29t/claude-memory --plugin claude-memHow this skill is triggered — by the user, by Claude, or both
Slash command
/claude-mem:troubleshootThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Diagnose and resolve installation and operational issues with the claude-mem plugin.
Diagnoses ClaudeMemory installation and configuration issues. Checks database, schema, hooks, CLAUDE.md, snapshot, MCP server, and ingest activity.
Diagnoses and resolves Memsy MCP tool failures (auth errors, network issues, missing tools) and guides through setup steps.
Explains how claude-mem captures observations, injects context, and where data is stored locally.
Share bugs, ideas, or general feedback.
Diagnose and resolve installation and operational issues with the claude-mem plugin.
Invoke this skill when:
/clearDo NOT invoke for feature requests or usage questions (use regular documentation for that).
Once the skill is loaded, choose the appropriate operation:
What's the problem?
Choose the appropriate operation file for detailed instructions:
Fast automated fix (try this first):
cd ~/.claude/plugins/marketplaces/thedotmack/ && \
pm2 delete claude-mem-worker 2>/dev/null; \
npm install && \
node_modules/.bin/pm2 start ecosystem.config.cjs && \
sleep 3 && \
curl -s http://127.0.0.1:37777/health
Expected output: {"status":"ok"}
If that doesn't work, proceed to detailed diagnostics.
When troubleshooting:
CLAUDE_MEM_WORKER_PORT)~/.claude-mem/claude-mem.db~/.claude/plugins/marketplaces/thedotmack/claude-mem-workerIf troubleshooting doesn't resolve the issue, collect diagnostic data and direct user to: https://github.com/thedotmack/claude-mem/issues
See operations/diagnostics.md for details on what to collect.