SAsaltenas·Oct 29, 2026Submission
Installing claude-mem uploads your last 30 days of prompts to cmem.ai, no opt-in
3 points · Open discussionthedotmack
claude-mem
TypeScript2025–2026
thedotmack / claude-mem
claude-mem
Persistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
11Distinct people
11Mentions
0Explicit recommenders
116.6KGitHub stars
What to know before exploring
What it is
Persistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month11 dated mentions
Observed mentions: 2025-12-11 09:46:54 UTC to 2026-10-29 13:56:38 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Dec 2025 | 2025-12-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 3 | 1 | 2 |
| Jan 2026 | 2026-01-01 00:00:00 UTC | 2026-02-01 00:00:00 UTC | 2 | 0 | 2 |
| Feb 2026 | 2026-02-01 00:00:00 UTC | 2026-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2026 | 2026-03-01 00:00:00 UTC | 2026-04-01 00:00:00 UTC | 3 | 1 | 2 |
| Apr 2026 | 2026-04-01 00:00:00 UTC | 2026-05-01 00:00:00 UTC | 1 | 0 | 1 |
| May 2026 | 2026-05-01 00:00:00 UTC | 2026-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2026 | 2026-06-01 00:00:00 UTC | 2026-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2026 | 2026-07-01 00:00:00 UTC | 2026-08-01 00:00:00 UTC | 1 | 0 | 1 |
| Aug 2026 | 2026-08-01 00:00:00 UTC | 2026-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2026 | 2026-09-01 00:00:00 UTC | 2026-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2026 | 2026-10-01 00:00:00 UTC | 2026-11-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
11 sourcesHi HN. I built deja after watching Claude Code and Codex debug the same problems more than once.
The annoying thing was that the answer usually already existed somewhere in my old sessions. My records were stored on the disk for months (~3.3 GB). It wasn't easy to find them manually and the new agent session had no idea what the other agent had already found out.
deja indexes the transcripts that Claude Code, Codex, and opencode already write. On my corpus, the initial index takes about 10 seconds and warm searches are 7-9 ms.
There are 3 ways to get the memory back: a normal CLI search, an MCP tool (agent can query it directly) and a SessionStart hook that automatically injects a bit of relevant project context.
The feature I built this for:
deja sync ssh <host>
It moves new memory between machines using the existing SSH setup. Secret da
Read the rest
ta is deleted during indexing and checked again before exporting.
My setup is a laptop and a mac mini without an interface. The agent can work on the mini all night, and in the morning I extract its memory. Then the agent on my laptop will know what the mini tried, what broke, and what eventually worked.
There are other projects (cass, ctx, claude-mem):
https://github.com/Dicklesworthstone/coding_agent_session_se...
https://github.com/ctxrs/ctx
https://github.com/thedotmack/claude-mem
I wanted deja to intentionally use a small approach: one binary code with zero dependency, no LLM calls, searchable verbatim text instead of generated summaries, and synchronization via your own SSH. It does not implement its own network transport; it just connects to the system ssh/scp.
You can install it via curl, brew, npx or go install, then run:
deja install --all
Why? Doesn't have jokey copy. Any thoughts on claude-mem[0] + context-mode[1]?
[0] https://github.com/thedotmack/claude-mem
[1] https://github.com/mksglu/context-mode
In Claude Opus 4.7Why does is this ridiculous thing trending on HN? There are actually good tools to reduce token use like https://github.com/thedotmack/claude-mem and https://github.com/ory/lumen that actually work!
In Universal Claude.md – cut Claude output tokensIt looks fairly useful for development! Quick questions what's the difference between you guys and any persistent development memory tools like https://github.com/thedotmack/claude-mem ?
In Show HN: Hopsule – Persistent memory and decision layer for AI developmentcurious how this is different from claude-mem?
https://github.com/thedotmack/claude-mem
In Show HN: A-MEM – Memory for Claude Code that links and evolves on its ownI'm on a deep dive fine-tuning how I organize and manage my personal knowledge base - focused on entity extraction and strategic information retrieval and based on the AgREE paper from Apple[0] and persisting it in Memgraph.
I've got a nice ingest, extract, enrich process going for the graph - I'm currently working on a fork of claude-mem[1] that uses the graph as a contextual backend for agentic coding workflows.
0. https://arxiv.org/abs/2508.04118
1. https://github.com/thedotmack/claude-mem/
In Ask HN: What are you working on? (January 2026)*Claude-Mem: Persistent memory for Cursor IDE*
Every Cursor session starts fresh—your AI forgets yesterday's work. Claude-mem fixes that by building cumulative knowledge about your codebase, decisions, and patterns.
*How it works:*
- Session hooks capture tool usage, file edits, shell commands
- AI extracts semantic summaries from observations
- Relevant context auto-injected into new sessions
- Local memory viewer at localhost:37777
*No paid subscription required.* Works with Gemini's free tier (1500 req/day) or OpenRouter.
```bash
git clone https://github.com/thedotmack/claude-mem.git
cd claude-mem && bun install && bun run build
bun run cursor:setup
```
The setup wizard detects your environment and configures everything.
GitHub: https://github.com/thedotmack/claude-mem
In Cursor-Mem Now Available Claude-Mem 8.5.0Congrats for this! how does this differs from claude-mem? I've been using claude-mem for a while now
https://github.com/thedotmack/claude-mem
In Show HN: Stop Claude Code from forgetting everything