Stevieclear Claude Mem Privacy Fork
stevieclear-claude-mem-privacy-fork is a Claude Code plugin for the Build phase that provides persistent compressed session memory while excluding non-Anthropic backends such as Gemini.
by StevieClear · github.com/StevieClear/claude-mem-privacy-fork
Run persistent Claude session memory with compression while refusing non-Anthropic memory backends such as Gemini.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install stevieclear-claude-mem-privacy-fork@StevieClear/claude-mem-privacy-forkBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:StevieClear/claude-mem-privacy-fork") and the paste-ready config with skillselion.get_install_config("plugin:StevieClear/claude-mem-privacy-fork").
What it does
stevieclear-claude-mem-privacy-fork is a one-plugin Claude Code bundle from StevieClear/claude-mem-privacy-fork for builders who want claude-mem-style persistence without shipping conversation-derived context to Google Gemini or other extra vendors. It advertises compression and cross-session memory so you spend less time re-explaining architecture, API contracts, and half-finished tasks. The fork’s positioning is ideological and practical: memory stays in the Anthropic-aligned path you already trust for coding chat. Solo founders juggling Validate through Operate benefit when a single product spans weeks of agent sessions. You still configure what gets stored and rotate keys as usual; this plugin does not replace backups or formal data policies—it reduces vendor sprawl in the memory layer.
Highlights
- Privacy-oriented fork of claude-mem with Anthropic-only memory stance (no Gemini)
- Persistent memory and context compression across Claude Code sessions
- Single-plugin bundle focused on session continuity for long builds
- Targets developers who want AI interactions limited to them and Anthropic
- Keywords emphasize mem, context, and cross-session persistence
Why builders use it
Builders who rely on claude-mem want continuity across sessions but reject forks or defaults that send memory work through Gemini or other third-party models.
After install, Claude Code can retain compressed context across sessions through this privacy fork’s single-plugin memory system without the NO GEMINI violation the authors call out.
At a glance
- Type - Plugin in AI Agents.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is stevieclear-claude-mem-privacy-fork for?
Developers who believe AI interactions and memory should stay between them and Anthropic and who want persistent Claude session context without Gemini.
When should I use stevieclear-claude-mem-privacy-fork?
Use it when multi-day Claude Code work on one codebase outgrows copy-paste context and you need compressed mem across sessions with a privacy-first fork.
How do I add stevieclear-claude-mem-privacy-fork to my agent?
Install the plugin from StevieClear/claude-mem-privacy-fork following that repo’s Claude Code plugin registration, then enable the mem system per upstream claude-mem-style setup in the fork docs.
Comments
Share how you use stevieclear-claude-mem-privacy-fork, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.