Pick up on another machine.
Cloud sync keeps captured project memory available when you move between your connected computers.
Explore cloud sync claude-mem + CMEM Pro
All your context.
Everywhere.
All at once.
The decisions, discoveries, and fixes from your work—ready for the next session, the next machine, and the next tool.
Free, open-source engine · 97.8k GitHub stars ↗
Claude Code · yesterday
We fixed the retry loop.
Keep the retry inside the transaction. Stop after three attempts. Add the decision to the project notes.
DecisionRetry policy for checkout
Three attempts, with backoff. A new request must keep the same idempotency key.
Source: project session · observation #142Saved to your context
DecisionsDiscoveriesFixesChatGPT · today
Why did we limit checkout retries?
To avoid duplicate charges when a request times out. The agent kept the same idempotency key and limited retries to three.
See how recall worksRecalls synced notes. ChatGPT conversations are not automatically captured.
Less starting over
Keep what you learned.
Get back to the work.
claude-mem keeps structured notes outside the chat. CMEM Pro makes that history available through your private MCP connection.
Find the useful detail.
Search decisions, discoveries, and fixes. Load the relevant notes instead of repeating the whole conversation.
See the memory loopUnderstand what happened.
Return to the history behind a change. Your notes keep the source and the work that led to the decision.
Explore your historyMore room for the task
Useful context.
Without the entire transcript.
Progressive recall lets your agent find a note before reading its details. Hosted observation moves memory generation off your primary agent’s subscription.
The effect on token use depends on your workload and provider. CMEM Pro does not change the price or limits of another subscription.
How memory formsFind the reason we kept SQLite.
01 · DecisionKeep local memory available offline.
Found the relevant note. Read details when needed.
02 · DiscoveryCloud sync is an additional layer.
The open-source engine keeps its local database.
Across your tools
A project has one history.
Your tools can share it.
Capture with a supported claude-mem setup. Recall synced memory from MCP clients, including ChatGPT when your account supports custom connectors.
Built in the open
See what people
are making with it.
The community uses claude-mem for coding, research, and tools of their own. Explore the projects and the people behind them.
97.8kGitHub starsAn open-source project by @thedotmack,
shaped by its contributors.
Choose your next step
Your memory.
Or your team’s shared context.
CMEM Pro
Hosted observation, cloud sync, and your private MCP link. 30 Day Free Trial. Then $30/month.
30 Day Free TrialTeamBrain pilot
Help shape shared memory with a team already using claude-mem. Pilot scope and onboarding are agreed together; public team pricing is not announced.
Explore the pilotA few useful answers
Before you connect.
Is claude-mem free?+
Yes. The local claude-mem engine is open source. CMEM Pro is the paid hosted observation and cloud sync service.
Does it capture everything in every tool?+
No. Capture depends on the tool and integration you install. MCP connections provide recall; connecting ChatGPT does not automatically capture ChatGPT conversations.
Where is my memory stored?+
The local engine stores memory on your machine. If you enable cloud sync, synced data is also stored by CMEM. Review the privacy policy before connecting.
Keep the useful part
Your next session
starts with context.
Install the open-source engine. Add CMEM Pro when you want hosted observation and cloud sync.