4 ms·
> Claude now automatically records and recalls memories as it works Neat: https://code.claude.com/docs/en/memory https://code.claude.com/docs/en/memory I gues
by neuronexmachina 9mo ago
> Claude now automatically records and recalls memories as it works
Neat: https://code.claude.com/docs/en/memory https://code.claude.com/docs/en/memory
I guess it's kind of like Google Antigravity's "Knowledge" artifacts?
- om8 9mo agoIs there a way to disable it? Sometimes I value agent not having knowledge that it needs to cut corners
- nerdsniper 9mo ago90-98% of the time I want the LLM to only have the knowledge I gave it in the prompt. I'm actually kind of scared that I'll wake up one day and the web interface for ChatGPT/Opus/Gemini will pull information from my prior chats.
- hypercube33 9mo agoI'm fairly sure OpenAI/GPT does pull prior information in the form of its memories
- nerdsniper 9mo agoAh, that could explain why I've found myself using it the least.
- sharifhsn 9mo agoGemini has this feature but it’s opt-in.
- vineyardmike 9mo agoAll these of these providers support this feature. I don’t know about ChatGPT but the rest are opt-in. I imagine with Gemini it’ll be default on soon enough, since it’s consumer focused. Claude does constantly nag me to enable it though.
- pdntspa 9mo agoThey already do this I've had claude reference prior conversations when I'm trying to get technical help on thing A, and it will ask me if this conversation is because of thing B that we talked about in the immediate past
- sanxiyn 9mo agoYou can disable this at Settings > Capabilities > Memory > Search and reference chats.
- sumtechguy 8mo agoHad chatgpt reference 3 prior chats a few days ago. So if you are looking for a total reset of context you probably would need to do a small bit of work.
- kzahel 9mo agoClaude told me he can disable it by putting instructions in the MEMORY.md file to not use it. So only a soft disable AFAIK and you'd need to do it on each machine.
- jsw97 9mo agoI ran into this yesterday and disabled it by changing permissions on the project’s memory directory. Claude was unable to advise me on how to disable. You could probably write a global hook for this. Gross though.
- codethief 9mo agoAre we sure the docs page has been updated yet? Because that page doesn't say anything about automatic recording of memories.
- neuronexmachina 9mo agoOh, quite right. I saw people mention MEMORY.md online and I assumed that was the doc for it, but it looks like it isn't.
- ruszki 9mo agoYeah, and I was confused by the child comments under yours. They clearly didn’t read your link.
- bityard 9mo agoIf it works anything like the memories on Copilot (which have been around for quite a while), you need to be pretty explicit about it being a permanent preference for it to be stored as a memory. For example, "Don't use emoji in your response" would only be relevant for the current chat session, whereas this is more sticky: "I never want to see emojis from you, you sub-par excuse for a roided-out spreadsheet"
- 9dev 9mo ago> you sub-par excuse for a roided-out spreadsheet That’s harsh, man.
- flutas 9mo agoIt's a lot more iffy than that IME. It's very happy to throw a lot into the memory, even if it doesn't make sense.
- anupamchugh 9mo ago[flagged]
- kzahel 9mo agoI looked into it a bit. It stores memories near where it stores JSONL session history. It's per-project (and specific to the machine) Claude pretty aggressively and frequently writes stuff in there. It uses MEMORY.md as sort of the index, and will write out other files with other topics (linking to them from the main MEMORY.md) file. It gives you a convenient way to say "remember this bug for me, we should fix tomorrow". I'll be playing around with it more for sure. I asked Claude to give me a TLDR (condensed from its system prompt): ---- Persistent directory at ~/.claude/projects/{project-path}/memory/, persists across conversations MEMORY.md is always injected into the system prompt; truncated after 200 lines, so keep it concise Separate topic files for detailed notes, linked from MEMORY.md What to record: problem constraints, strategies that worked/failed, lessons learned Proactive: when I hit a common mistake, check memory first - if nothing there, write it down Maintenance: update or remove memories that are wrong or outdated Organization: by topic, not chronologically Tools: use Write/Edit to update (so you always see the tool calls)
- ra7 9mo ago> Persistent directory at ~/.claude/projects/{project-path}/memory/, persists across conversations I create a git worktree, start Claude Code in that tree, and delete after. I notice each worktree gets a memory directory in this location. So is memory fragmented and not combined for the "main" repo?
- vardalab 9mo agoYes, I noticed the same thing, and Claude told me that it's going to be deleted. I will have it improve the skill that is part of our worktree cleanup process to consolidate that memory into the main memory if there's anything useful.
- 4b11b4 9mo agoI understand everyone's trying to solve this problem but I'm envisioning 1 year down the line when your memory is full of stuff that shouldn't be in there.
- pdntspa 9mo agoI thought it was already doing this? I asked Claude UI to clear its memory a little while back and hoo boy CC got really stupid for a couple of days
- deleted 9mo ago[deleted]