A memory plugin for Codex and Claude Code that preserves engineering knowledge, repository context, and working preferences across coding sessions. It automatically captures lessons from completed work, maintains architecture and procedural knowledge, and retrieves relevant context to accelerate future tasks.
A memory plugin for AI coding that turns engineering experience, repository knowledge, and your way of working into memory that remains useful in future tasks.
172Stars
9Forks
1Open issues
1Watching
JavaScript MIT Updated 6 days ago
README
Make Every Interaction the Starting Point for the Next
Coding agents are good at the task in front of them, but a new session often starts without the architecture, failed attempts, repository rules, or working preferences established before it.
MemoraX Code gives Codex, Claude Code, and OpenCode a shared memory layer for that context. It can recall prior engineering knowledge, capture reusable lessons from completed work, maintain repository knowledge, and carry your procedures and preferences into future sessions.
The goal is not to remember everything. It is to bring back the small amount of memory relevant to the current task so the agent can reach useful investigation and validation sooner.
Quick Start
Prepare Node.js 24+ and at least one of Codex, Claude Code, or OpenCode. Python 3 is required for Repo Memory operations.
Install and Connect
1. Get a MemoraX Memory Key
Sign up at MemoraX Console and create an API key. Enter the key only in your local installation terminal; do not paste it into chats or public issues.
2. Install and Follow the Prompts
npm install -g @memorax/memorax-code --foreground-scripts
Keep --foreground-scripts so the complete setup remains visible. The
installer automatically detects available Codex, Claude Code, and OpenCode
clients and connects the clients it finds. Follow the prompts to enter your
Base User ID, preferred language, and API key. Codex users must also approve
Hook activation and trust when prompted. Restart or refresh every detected
client after installation before starting a new session.
If setup is skipped or cannot prompt, the package remains installed but MemoraX-backed search, retrieval, and writeback remain unavailable.
Try Cross-Session Memory
Clone the example repository from the product website, then open Codex, Claude Code, or OpenCode in the project directory:
git clone https://github.com/SWE-agent/test-repo.git
cd test-repo
Invoke the Skill as $memorax-code in Codex or /memorax-code in Claude Code.
In OpenCode, ask the agent to use the memorax-code skill by name. The prompts
below use its product name and work in all three clients.
Send these prompts in order in the same session:
- Use the MemoraX Code skill to build Repo Memory, retrieving only the latest 3 issues, pull requests, and commits.
- Review the recent Repo Memory issue: the zeroth number was once calculated incorrectly. Avoid repeating the same problem now.
- Use the MemoraX Code skill to remember the engineering lesson from this coding task.
Close the current conversation, start a new session in the same repository, and send:
Use the MemoraX Code skill to recall the earlier engineering lesson and suggest what to check.
The agent should retrieve the saved lesson and use it to make suggestions for the current repository.
[!TIP] The prompts above are only for quick verification. In normal use, you do not need to invoke the MemoraX Code skill to add memory manually. It writes relevant memory in the background and guides agents to search when useful. You can view content-free local activity and status in the Memory Viewer.
Four Clear Memory Boundaries
| Memory | The question it answers | Examples |
|---|---|---|
| Coding Memory | What engineering lessons should carry into the next task? | Verified fixes, failed approaches, design rationale, pitfalls, and regression checks |
| Repo Memory | What should an agent know about this repository? | Architecture maps, module ownership, entry points, and commit/PR/MR/issue evidence |
| Personal Memory | How should the agent communicate and collaborate with you? | User Profile preferences such as language, tone, explanation depth, and result format |
| Procedure Memory | How should this kind of task be carried out? | Reusable steps, checklists, prerequisites, exceptions, and validation gates |
Product Capabilities
| Capability | What it does |
|---|---|
| Background memory writeback | Extracts reusable knowledge from completed turns and writes it to Coding Memory in the background. |
| Preference continuity | Records User Profile preferences and injects them into future tasks on a configured cadence. |
| Procedure reuse | Records reusable task procedures and reminds future agents to apply them. |
| Background Repo Memory maintenance | Automatically organizes repository structure, entry points, and history evidence in the background, then updates them according to policy to reduce repeated searching and summarization. |
| Active memory control | Lets you search and add memory through the bundled MemoraX Code skill or the CLI. |
| Client integration | Integrates with Codex, Claude Code, and OpenCode to trigger memory retrieval, reminders, and writeback. |
| Local visualization | Uses the local Memory Viewer to summarize activity counts, retrieval, and writeback status. |
Your Memory, Your Control
MemoraX is required for cloud-backed memory. Entering a Base User ID and API key after the installer's disclosure activates MemoraX search/add and the generated configuration's automatic writeback; there is no second writeback confirmation. Automatic retrieval remains off until explicitly enabled.
Active memory operations send their query or selected content to MemoraX. Automatic writeback sends selected user instructions and the matching final Agent response from trusted workspace turns for extraction and storage. It does not upload the complete retained client trace artifact or local trace path.
Sign in to MemoraX Console at any time to view, edit, or delete saved memories. MemoraX Cloud does not receive model-provider credentials or local Backend tokens.
Read Configuration for all settings and Security for network, local-data, and retention boundaries.
Update
For a global npm installation:
memorax-code update
The command follows the installed release channel and preserves configuration. Restart or refresh Codex, Claude Code, and OpenCode when a release changes plugin assets or skills.
Uninstall
Run the product lifecycle before removing the npm package:
memorax-code uninstall
This removes managed integrations and the global package while retaining
MEMORAX_CODE_HOME (default ~/.memorax-code), Claude plugin data, provider
configuration, and memories stored in MemoraX. Remove retained local or cloud
data separately only after reviewing what you still need.
Documentation
Develop and Contribute
Issues and pull requests are welcome. Read CONTRIBUTING.md before making a change, and never include API keys, raw transcripts, private memory, or local trace artifacts in a public report.
License
MemoraX Code is available under the MIT License.
Comments (0)
Sign in to join the discussion.
No comments yet
Be the first to share your take.