Product upvotes vs the next 3

Waiting for data. Loading

Product comments vs the next 3

Waiting for data. Loading

Product upvote speed vs the next 3

Waiting for data. Loading

Product upvotes and comments

Waiting for data. Loading

Product vs the next 3

Loading

Claude-Mem

An AI that takes notes on other AI's work in real-time

Transform ephemeral AI conversations in REAL-TIME as a permanent, searchable archive. Visualize development timelines, track decisions across commits, and collaborate with your team.

Top comment

You know that moment when you open a new Claude session and realize you have to explain everything again? "So we decided to use SQLite because—" Stop. Claude doesn't remember. You're strangers again. That frustration is why I built claude-mem. AI assistants have amnesia. For quick questions, it doesn't matter. But real software projects span weeks. You make decisions on Tuesday that matter on Friday. You debug for three hours and finally find the root cause. That insight should persist—but it doesn't. Every session starts from zero. The naive solution was obvious: save conversations, search later. Tried it. Useless. Thousands of tokens of noise. What matters isn't the forty-seven files Claude opened—it's the moment you realized why the bug happened. Memory isn't storage. It's compression. So claude-mem watches Claude work, captures what matters, compresses it, and injects it into future sessions. Invisibly. You don't see memory forming—it just happens. Context arrives before you notice it was missing. The whole thing was built using itself. This comment? Written by Claude searching its own memories of the last ten weeks of development. Would love to hear how others are thinking about AI memory and continuity. What would you want an AI assistant to remember?