Menu
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.
Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.
| name | memorix-troubleshooting |
| description | Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing. |
Prefer direct CLI diagnostics first. MCP is an integration surface, not the only way to operate Memorix.
| Symptom | Check | CLI fallback |
|---|---|---|
| MCP tools missing | host MCP config and restart | memorix setup --agent <agent> |
| Unsure project is bound | project status | memorix status and git status |
| HTTP MCP stale or unbound | background health and explicit session bind | memorix background status; then memorix session start --projectRoot <path> |
| Hooks not firing | hook status | memorix hooks status |
| Need to inspect generated files | preview | memorix hooks preview --agent <agent> |
| Setup looks incomplete | reinstall host integration | memorix setup --agent <agent> |
| Need dashboard/control plane | background service | memorix background start or memorix serve-http --port 3211 |
memorix serve) for normal host-launched MCP integration.projectRoot and remember that visually similar junction paths may bind different session histories.