Stevieclear Claude Mem Privacy Fork
- Updated February 1, 2026
- StevieClear/claude-mem-privacy-fork
stevieclear-claude-mem-privacy-fork is a Claude Code plugin that provides persistent compressed session memory while excluding non-Anthropic backends such as Gemini.
About
stevieclear-claude-mem-privacy-fork is a one-plugin Claude Code bundle from StevieClear/claude-mem-privacy-fork for developers 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. 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.
- 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
Stevieclear Claude Mem Privacy Fork by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install stevieclear-claude-mem-privacy-fork@StevieClear/claude-mem-privacy-forkAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| Last updated | February 1, 2026 |
|---|---|
| Repository | StevieClear/claude-mem-privacy-fork ↗ |
What it does
Run persistent Claude session memory with compression while refusing non-Anthropic memory backends such as Gemini.
Who is it for?
Privacy-conscious developers already on Claude Code who need long-running project memory and explicit Anthropic-only processing.
Skip if: Skip if you want multi-vendor memory routing, cloud dashboards, or zero local persistence overhead.
What you get
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.
- One registered claude-mem privacy-fork plugin in Claude Code
- Cross-session memory and compression behavior per fork configuration
- Memory pipeline aligned with Anthropic-only requirements stated by the authors
Recommended Plugins
0pg Cc MarketplacePersonal Claude Code plugins collection
1shot Labs Squadron Comms PluginVoice communication system with ElevenLabs TTS for multi-agent coordination in Claude Code3
23blocks Os Ai MaestroAI Agent Orchestrator with Skills System - Give AI Agents superpowers: memory search, code graph queries, agent-to-agent messaging.733
3commas Io Commas ClaudeThis is a repo with shared agents and skills used company-wide4
884js Agent Plugins1 plugin
A5c Ai BabysitterBabysitter enforces obedience to agentic workforces and enables them to manage extremely complex tasks and workflows through deterministic, hallucination-free self-orchestration1.6kHow it compares
Anthropic-aligned memory fork, not a general LLM integration pack or marketplace of unrelated skills.
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.