Share local project memory across coding agents with Memorix
Use Memorix when multiple coding agents or sessions need a shared, searchable, local-first project memory instead of isolated chat history.
npx skills add agentskillexchange/skills --skill share-local-project-memory-across-coding-agents-with-memorix
Use Memorix when a coding project needs memory that survives new chats, IDE switches, terminal sessions, and handoffs across agents. The operator initializes a local-first project memory, sets up supported agents, and exposes compact memory/context tools through MCP, hooks, rules, skills, or generated agent integrations. Agents can then retrieve project context, store durable observations, inspect session summaries, and reuse decisions without re-reading the whole project or asking the user to repeat prior work.
What this skill actually does
Invoke this instead of using one product’s built-in history when the same repository is handled by Claude Code, Codex, Cursor, Gemini CLI, OpenCode, OpenClaw, or another MCP-capable coding agent. It is a fit for teams or solo operators who switch agent runtimes, run parallel coding sessions, or want Git-derived and reasoning memory available from a local store.
The boundary is project-scoped coding-agent memory setup and operation. This is not a generic database, a personal notes app, or a broad agent framework listing. A good skill should initialize Memorix, connect the chosen agent, retrieve only task-relevant project memory, write reviewable durable facts, and keep memory use tied to the current repository.