 | Nemp Memory |
Smart memory for AI agents — Claude Code & OpenClaw
The Problem
Claude Code forgets everything between sessions. You waste 15-20 minutes every day re-explaining:
- Your tech stack
- Architecture decisions
- Project patterns
- What you worked on yesterday
Other memory plugins exist, but they're complicated:
- Require MCP servers, SQLite databases, or Ollama
- Need cloud accounts and API keys
- Send your code context to their servers
- Need 10+ steps to set up
- Come with web UIs you'll never use
- Store data in formats you can't easily read
Why Nemp Is Different
Nemp is stupidly simple:
/plugin marketplace add https://github.com/SukinShetty/Nemp-memory
/plugin install nemp
# Done.
Zero dependencies. No cloud. No API keys. Plain JSON files. Just works.
Cross-platform: Works on Claude Code, OpenClaw, and any AgentSkills-compatible platform. One memory store, multiple agents.
| Feature | Other Plugins | Nemp |
|---|---|---|
| Setup | 10+ steps | 2 commands |
| Dependencies | SQLite, Ollama, web servers | None |
| Cloud Required | Often yes | No |
| API Key Required | Often yes | No |
| Data Storage | Binary databases, cloud | Plain JSON |
| Privacy | Data may leave your machine | 100% Local |
| Auto-detect Stack | No | Yes |
| Proactive Suggestions | No | Yes |
| Auto-sync to CLAUDE.md | No | Yes |
| Two-way CLAUDE.md sync | No | Yes |
| Conflict detection | No | Yes |
| Works Offline | Sometimes | Always |
| Cost | Free to $19/month | Free Forever |
What's New in v0.2.0
| Feature | Description |
|---|---|
| Agent ID Tracking | Every memory records which agent wrote it — main, nemp-init, backend, etc. |
| Access Logs | All read/write/delete operations logged to .nemp/access.log with timestamps and agent names |
/nemp:log Command | View the full audit trail. Filter by agent, tail recent entries, or clear the log |
| Token Compression | /nemp:save compresses values before storing — ~70% smaller, preserves all technical terms |
/nemp:init Optimized | Single bash scan, reads only package.json, writes all memories in one operation |
| MEMORY.md Index | Auto-generated index at .nemp/MEMORY.md with agent attribution and quick overview |
6 Features That Set Nemp Apart
1️⃣ Auto-Init: One Command Learns Everything
Unique to Nemp: Auto-detects your entire stack in one command.
/nemp:init
That's it. Nemp scans your project and automatically detects:
- Framework (Next.js, React, Vue, etc.)
- Language & config (TypeScript, strict mode)
- Database & ORM (Prisma, Drizzle, MongoDB)
- Auth solution (NextAuth, Clerk, Supabase)
- Styling (Tailwind, styled-components)
- Package manager (npm, yarn, pnpm, bun)
Example output:
Scanning your project...
I found:
Framework: Next.js 14 (App Router detected)
Language: TypeScript (strict mode enabled)
Database: PostgreSQL via Prisma
Auth: NextAuth.js
Styling: Tailwind CSS
Package Manager: npm
Saved 6 memories in 2 seconds
Claude now knows your stack forever.
Why this matters:
- New team members: Zero onboarding
- Context switching: Instant project recall
- No manual documentation needed
2️⃣ Smart Context: Find Memories Instantly
Unique to Nemp: Semantic search that understands what you're looking for.
/nemp:context auth
Nemp doesn't just search for "auth" — it expands to:
- authentication, login, session, jwt, oauth, nextauth, clerk, token, passport, credentials...
Example output:
FOUND 3 MEMORIES MATCHING "auth"
auth-provider [KEY MATCH]
NextAuth.js with JWT strategy