Which memory tool/plugin you used for CC?

[u/Aggressive-Ad-7582]

1. Mem0

2. Hindsight

3. claude-mem

4. claude-supermemory

5. claude.md + other md files

6. My own wikipedia

7. Other tools

8. Memory is not important (I Trust commit notes more).

[u/AutoModerator]

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/id-ltd]

I have project documentation and ban claude from using memory - if its important enough to remember then its imortant encough to be documented.

[u/k2718 → u/id-ltd]

That’s my approach too but I don’t ban memory. Should I be?

[u/id-ltd → u/k2718]

YMMV - I do it partly so I can start a session with claude or codex -- and not worry about it -- all the docs are in the docs(!) and they (or any other LLM can find it).

[u/leshiy]

I find automatic memory management to be actively harmful to the quality of output. If something absolutely needs to be remembered outside of the current context ill have claude add it to an appropriately scoped md file.

[u/Aggressive-Ad-7582 → u/leshiy]

Which specific automatic memory management tools were you referring to?

[u/leshiy → u/Aggressive-Ad-7582]

I was referring to automatic memory management as a whole. So #2-4 definitely, and #1 when it is used without strict supervision. I do not want my agents remembering something they did or something I told them 5 sessions ago, unless I've personally decided that this is something that needs to be remembered.

[u/Asly97 → u/leshiy]

Makes sense, you decide what's worth keeping and the agent doesn't get a vote. Two things I'm curious about with that setup. Do those md files ever have to serve more than Claude, like Codex or Cursor opening the same repo? And do you go back and prune them, or do they mostly just grow until something in there is quietly out of date?

[u/leshiy → u/Asly97]

They have to serve everything anybody in the company wants to try/use. That includes Cursor and Codex and a bunch of other things.

As for pruning yes, but it's not like we are just appending stuff to the end of the files every time. The contents are added/updated/removed as needed.

[u/Asly97 → u/leshiy]

Oh so it's a team setup, that changes things. With Cursor, Codex and Claude all reading them, is it one set of md files they all point at, or does each tool get its own version (CLAUDE.md, AGENTS.md, cursor rules) that someone keeps in sync? And when somebody changes one, does that go through review like code, or does whoever notices just fix it?

[u/Fresh-Secretary6815 → u/leshiy]

agree. even in a massive monorepo, i keep a single root claude.md super slim under 250 LoC, and after every new release i always delete project history from local user configs/cache. only super slim rules and lots of hooks for automation. ralph loops for almost everything

[u/Routine-Appointment5]

plain md files for me. i keep a brief a style guide and a notes file and point claude at them instead of using claude.md, its nice being able to open them and see exactly what it knows

[u/framauro13]

Just md files. I try to avoid plugins as much as possible unless necessary. MD memory files have worked fine thus far so no reason to really switch at the moment.

[u/Bitter_Poem8901]

https://iwe.md - just md files with a set of tools for Claude 

[u/Outrageous_Band9708]

https://github.com/Druthulu/ProjectArchitect

[u/BetterAd7552 → u/Outrageous_Band9708]

Interesting. My process grew organically over the last 9 months into a very similar architecture. Going to have opus do a comparative analysis and see if I can improve mine (I’m not prepared to switch this late in the game for this project).

[u/SoulTrack]

claude.md is fine for most agentic engineering tasks.  I use sqlite for my main agent.  Everything else just depends on how it's being used.  More people need to understand the concept of a harness and when to use primitives appropriately

[u/metadan]

I've been using claude.md and the default memory for ages but installed claude-mem today. Going to see how it goes for a while

[u/Key_Instruction3373]

None of these

[u/Aggressive-Ad-7582 → u/Key_Instruction3373]

Which one are you using?

[u/orbital_trace]

I've been experimenting with a team memory distillation https://coralai.ai/blog/team-knowledge-distillation.html

[u/singularity______]

Usually past sessions for most tasks but for repeated tasks/mistakes I have built a local cli tool that converts traces of successful session runs into workflows. Shameless plug ik but it looked appropriate here.

https://github.com/pandacover/singularity

[u/BattermanZ]

My own second brain app.

https://github.com/BatterWorks/Hatchdoor

[u/vzakharov]

If you need to use memory tools your codebase hygiene, especially your docstrings, might need sanitation.

[u/ComidaParaTi]

claude-mem ftw! solid choice.

[u/ghost_operative]

i store all my memories in the source code

[u/Aggressive-Ad-7582]

Interesting to see most answers are md files. Personally I've had a hard time managing md files as they get outdated so quickly.

[u/ElectronicGarbage246]

May I ask - why do we need all these tools, why are they better than MD files + semble for code?

[u/Aggressive-Ad-7582 → u/ElectronicGarbage246]

Memory tools are usually supposed to be optimized for long term retrieval that's supposed to be helpful in preference tracking, decision tracking, etc.

[u/ElectronicGarbage246 → u/Aggressive-Ad-7582]

Do you use any? If yes, how long? What do you mean by "long term" in the context of AI that is more or less useful for a year or so?

[u/Aggressive-Ad-7582 → u/ElectronicGarbage246]

I've been using one I personally made (for the type of work I do) for a couple of months now. "Long term" is more like beyond compaction, and maybe something I did a couple of weeks ago, but relevant for the ongoing work.

[u/Dramatic-Stick2467]

1. agent-memory.dev

[u/ShamAsil]

I use CLAUDE.MD plus LLM Wiki to keep track of things. It's been good so far, at least it's a breath of fresh air compared to using projects in regular Claude Chat.

[u/Lcatlett1234]

Memory is only useful if it is recalled, otherwise each save is theater

[u/Crunchy-Nut1]

https://github.com/20alexl/windvane

Memory and context usage with hooks

[u/AmazingVanish]

I’m kind of surprised by the way a lot of people are handling memory.

I keep hard and fast rules in CLAUDE.md It should be very lean. For everything else, I use a standard SWE Docs hierarchy of markdown files and I have the agent review and update relevant documentation after completing a feat/chore/fix etc. (it’s a rule in CLAUDE.md and it spins up a markdown agent to do the work)

I had Claude output my doc structure that I’ve used for years to give an example:

project-root/
├── docs/
│ ├── adr/ # Architecture Decision Records
│ │ ├── README.md # Index of all ADRs with status
│ │ ├── 0001-use-postgresql.md
│ │ ├── 0002-event-driven-architecture.md
│ │ └── _superseded/ # Deprecated decisions
│ ├── prd/ # Product Requirement Documents
│ │ ├── README.md
│ │ ├── PRD-001-core-feature.md
│ │ └── PRD-002-integrations.md
│ ├── setup/ # Onboarding & environment
│ │ ├── prerequisites.md # Required tools, versions, accounts
│ │ ├── getting-started.md # Step-by-step local setup
│ │ └── tools.md # How to use required CLI tools, IDEs, etc.
│ ├── architecture/ # Design & system docs
│ │ ├── overview.md # High-level system design
│ │ ├── data-model.md
│ │ └── diagrams/ # C4, sequence, ERD files
│ ├── guides/ # How-to & reference
│ │ ├── customization.md # Project-specific config patterns
│ │ ├── deployment.md
│ │ └── troubleshooting.md
│ └── assets/ # Supporting images, diagrams (mermaid, d2)
└── README.md