
Thedotmack
Install claude-mem so Claude Code compresses and reuses session context instead of losing thread every time you restart.
Overview
thedotmack (claude-memory) is a plugin marketplace for the Build phase that installs claude-mem persistent session memory and context compression for Claude Code.
What is this marketplace?
- claude-mem plugin for persistent Claude Code memory across sessions
- Context compression to reduce repeated preamble and stale re-reads
- Marketplace id thedotmack bundling Alex Newman plugins
- Plugin version 12.1.0 in the published manifest
- Focused scope: memory system rather than full methodology or test MCP
- Marketplace ships 1 plugin named claude-mem at version 12.1.0
- Publisher metadata points to github.com/thedotmack/claude-mem
- Plugin description emphasizes persistent memory and context compression across sessions
What problem does it solve?
Claude Code forgets prior session context, forcing you to re-upload state and wasting tokens on repeats.
Who is it for?
Solo builders who run long Claude Code sessions across days and want lightweight persistent memory without running a full codebase graph.
Skip if: Teams that need symbol-level repo graphs, formal plan review tooling, or compliance-grade memory audit trails out of the box.
What do I get? / Deliverables
After install, claude-mem persists and compresses cross-session context so you pick up work without rebuilding the entire narrative.
- Installed claude-mem plugin (manifest version 12.1.0)
- Cross-session memory retention for ongoing Claude Code work
- Reduced need to manually replay project context each session
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Persistent memory plugins are catalogued under Build agent-tooling because that is when you configure how the agent retains state, even though benefits appear in every phase. Context compression across sessions is core agent infrastructure, not a ship-only test tool or launch SEO tactic.
How it compares
Session memory compression plugin, not Tessera-style SQLite graph methodology or TestDino QA MCP.
Common Questions / FAQ
Who is Thedotmack claude-memory for?
Indie developers using Claude Code who want persistent memory and context compression between sessions without a heavy methodology stack.
When should I use claude-mem?
Use it journey-wide whenever repeated session restarts erase decisions, conventions, and in-progress task state.
How do I add claude-memory to my agent?
Register the Alamator/claude-memory (Thedotmack) marketplace in Claude Code and install the claude-mem plugin from the bundled plugin path.