Nemp Memory: project memory for Claude Code in local files
Nemp Memory
A Claude Code plugin that keeps project decisions and conventions in local .nemp files: save, find in a new session, update by key
- 140 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The plugin writes memory files to the project and home directory and edits `CLAUDE.md` during auto-sync
- Saved entries influence the agent in later sessions, so delete an incorrect entry
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/nemp-memoryDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The plugin writes memory files to the project and home directory and edits `CLAUDE.md` during auto-sync
- Saved entries influence the agent in later sessions, so delete an incorrect entry
This is third-party code. Review the repository files before installing.
What it does
Nemp Memory is a Claude Code plugin that gives project context a home in editable files. Project knowledge lives in `.nemp/` and preferences shared across projects in `~/.nemp/`. It works through Markdown commands: Claude Code reads and writes files following the plugin's instructions, and there is no background service. The core loop is: `/nemp:save` stores a decision under a key, `/nemp:recall` finds it in the next session, and saving again under the same key updates the entry. `/nemp:init` detects a JavaScript or TypeScript stack from `package.json`, `/nemp:save-global` keeps preferences for all projects, `/nemp:context` gathers related context and `/nemp:forget` removes stale entries. For review there are `/nemp:list`, `/nemp:health` with an 80-point diagnostic checklist and an access log. `/nemp:auto-sync on` enables `CLAUDE.md` updates after memory changes, and `/nemp:sync` compares the file with memory. Search is keyword-based with expansion and has no embedding service. Nemp Open version 0.3.0 is free and MIT licensed.
Who it is for. Developers in Claude Code who are tired of repeating the stack, conventions and reasons for decisions to the agent in every new session.
Good fit when
- At session start the agent should know the chosen decisions: REST for the public API, GraphQL internal only
- A JavaScript or TypeScript project has to be described to the agent quickly with one command
- Preferences such as commit style should carry across projects
- A decision changed and the old entry has to be updated under the same key
- The `CLAUDE.md` file should update from memory after decisions are saved
Not a fit when
- You do not work in Claude Code: the plugin is tied to its commands and other interfaces are experimental
- You need meaning-based search: this one is keyword search with no embeddings
- You want automatic self-learning memory: the loop is run by the agent and the user, and auto-learning is a plan
- You need the paid Cortex, Foresight, Decay and Import features: in this build they are only notices
Example request
Save under the key api-style the decision: public API on REST, GraphQL internal only. Then recall it and show what is in the project memory.Limitations
Claude Code is required: the plugin commands define agent actions and do not run as a separate program, so quality depends on how closely the agent follows them. Search is by keyword, and entries need clear keys.
Automatic learning, validated corrections and reversible archival are future work. The paid Nemp Pro tier is announced, and the Cortex, Foresight, Decay and Import features only print notices in the build. The last commit in the repository was made on October 1, 2026.
How to disable. Remove the plugin with `/plugin uninstall nemp`. The memory sits in the project's `.nemp/` directory and in `~/.nemp/`, and you can delete those folders by hand.
FAQ
How do I install Nemp in Claude Code?
Run `/plugin marketplace add https://github.com/SukinShetty/Nemp-memory` and `/plugin install nemp@nemp-memory`. If the `/nemp:` commands do not appear, restart Claude Code.
Where is the memory stored?
Project knowledge sits in `.nemp/` inside the repository and shared preferences in `~/.nemp/`. These are JSON files that you can open and edit by hand.
How do I update a saved decision?
Save under the same key with `/nemp:save`, for example `api-style` with a new value. A stale entry can be removed with `/nemp:forget`.
What does /nemp:health do?
It runs an 80-point diagnostic of the memory state and points out what needs attention. An access log viewer sits alongside.
Is a paid version required?
No, Nemp Open 0.3.0 is free under the MIT licence and covers the save, find and update loop. Nemp Pro is only planned, and its features show notices in the build.
Discussion
No questions or reviews yet.
Related
PluginsThe Supermemory plugin for Claude Code: persistent memory across sessions with automatic prompt recall, conversation capture and a codebase index
Agent memory as a graph of linked facts: decisions and errors outlive the session, with no vector database or paid API calls
A local workbench for Claude Code, Codex, Pi and OpenCode: memory changes wait for your review, then an audit follows each turn
A long-term memory plugin that keeps decisions, preferences and task state across sessions and injects only what a query needs
hipocampus gives an agent file-based memory: a 3,000-token topic index loads each session and shows what came up before
Claude Code Memory Setup: Obsidian-based memory
Claude Code Memory Setup
A guide with ready files: Claude Code keeps decisions between sessions through an Obsidian vault and /save and /resume commands
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Nemp Memory: project memory for Claude Code in local files (this card) | no | 140 | ||
| Claude-Mem | no | 116,457 | captures session history automatically, while Nemp keeps entries by key by hand | |
| Basic Memory | no | not required | 4,566 | Markdown notes over MCP for any client, while Nemp works as a Claude Code plugin |
README in short
The README lays out the idea of memory that evolves with the work and a save, use and keep-current loop. Tables show what commands do at each step and what works today. Links lead to the setup guide, the roadmap and the status of integrations with other tools.