Claude Code vs claude-mem

Claude decides what’s worth saving and sorts notes into four kinds, skipping what the code already shows. There’s no importance score. source

The observer is told what's worth recording and to skip routine steps, and it labels each note (bugfix, decision…). There's no importance score. source

The docs describe four kinds of note and never mention weighting by feeling.

No emotional weighting. Notes are sorted by the kind of work, not by feeling.

Notes stay until you or Claude edit or delete them, and they’re kept out of the old-transcript cleanup. The 200-line index cap is a size limit, not fading. source

Nothing fades note by note, but meaning-based search only looks back 90 days by default, and the start of a session shows just the newest notes. source

Each note carries its last-changed date, and when the index gets long Claude is told to merge or drop stale entries. Old and new are sorted out by Claude’s judgement. source

Exact copies within a session are dropped, but a newer note that contradicts an older one is simply stored beside it. source

Notes load by their place in the index or when Claude opens them. The only date kept is when a note was last written, so reading one doesn’t strengthen it. source

Being found doesn't strengthen a note. A usage counter exists in the database, but nothing updates it yet. source

Their open fix plan (issue #3609) says the counter will go up each time a note is recalled.

The always-loaded index works as signposts to the notes behind it. There are no automatic links between notes. source

Notes are tied to their files and their moment in a session, and a timeline tool brings up what happened just before and after one. Notes aren't linked to each other. source

Folder CLAUDE.md files and path rules come back on their own when Claude touches matching files, but only for rules you wrote. Its own notes wait to be opened. source

When Claude opens a file it has notes on, that file's history is added on its own. There are no reminders for a set time. source

Claude tidies the index when it nears its size limit, moving detail into topic files and merging entries, but during a session. No pass between sessions is documented. source

Nothing reworks notes between sessions. A summary is written after each reply, but old notes stay as first written.

Claude edits a note in place when things change and the date updates, but the docs describe no history of what it said before. source

Nothing corrects an old note when it's contradicted; old and new sit side by side.

Notes are lessons drawn from sessions (corrections, approaches you confirmed), written by Claude rather than a separate mechanism. source

Each reply's summary records what was learned, and on request a “knowledge agent” answers questions from hundreds of notes at once. No lasting general lessons are written. source

Notes about you and the project are read every session and shape how it works, but new facts aren’t explicitly weighed against them. source

No beliefs about people or projects. An optional CLAUDE.md per folder lists recent activity, not conclusions.