memorix

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.

Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether session_start is useful.

Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.