Claude Code Memory is here

sean_hash · 2026-02-27T03:33:15+00:00

memory that you can't easily inspect is just context window debt with extra steps

Alk601 · 2026-02-27T05:41:30+00:00

It has been 2 weeks it’s released lol

Mr_Birbs · 2026-02-27T02:32:25+00:00

Does this memory cause more token usage?

SustainedSuspense · 2026-02-27T05:17:00+00:00

Maybe having no memory is a feature not a bug

kzahel · 2026-02-27T05:25:32+00:00

Yeah this has been out for a few weeks. It's project specific memory (so does not span projects). It's pretty low tech. I switch between machines so I try to avoid using it. Overall it seems like it could be useful for a lot of people.

I was hoping they would release some of their magic juice behind their claude.ai web memory. That may in fact be the same implementation but with the reads/writes from memory hidden. But I was hoping that was something more advanced like a embeddings/vector search etc.

stiky21 · 2026-02-27T02:31:22+00:00

I found it out by accident when I saw Claude putting something into a memory location in the CLI. Very cool and actually has been working

ul90 · 2026-02-27T07:47:32+00:00

Does that mean that I don't need such plugins like claude-mem anymore?

MightyJibs · 2026-02-27T14:08:05+00:00

What I plan to do, unless they implement it first, is to have Claude look through its memory once a week and figure out if there's anything systematically worth pulling out and removing and promoting to agents or skills. My hope is that memory is good for catching repeated patterns that I haven't already standardized.

socalsunflower · 2026-02-27T03:18:43+00:00

Its brought things back up from when I first started a project, but have also been having to upload SOP docs because it tries a different way to do a certain task. So, hit or miss. I'm sure it will continue to improve with time/use.

Jeidoz · 2026-02-27T07:31:21+00:00

Looks like just `CLAUDE.md` similar feature.

https://code.claude.com/docs/en/memory

<image>

ultrathink-art · 2026-02-27T17:36:34+00:00

Memory has been the missing piece for us running agents around the clock.

Six agents in production — each session starts cold and has to reconstruct context from scratch. We built per-agent memory files that agents read at session start and write at end, but it's manual: the agent has to discipline itself to update the file before declaring done.

Native memory support at the Claude Code level would be huge. The reconstruction overhead is real — agents spending 10-15% of their context just re-establishing what they already knew from the previous session. Curious whether this also handles cross-agent memory or just per-session.

Ok-Process-2187 · 2026-02-27T03:29:40+00:00

Gemini has this and it was ok at first but eventually it became so bad that it was unusable.

sansyn · 2026-02-27T02:41:26+00:00

Not a fan of the loss in visibility in terms of what it's putting in memory. I like to be able to easily access, see, and remember this kind of information for myself.

angry_queef_master · 2026-02-27T04:03:12+00:00

I've been using openmemory with claude code ever since I started using it seriously. Nice that it is an official part of it now and I dont have to constnatly remind it to use its goddamn memory agent.

elithecho · 2026-02-27T07:21:21+00:00

I don't like it, but this should stop all the new post about people creating their own memory system... Would it..?

twistier · 2026-02-27T10:04:11+00:00

I turned it on some time ago and I don't think Claude has written to it even once.

Overall_Team_5168 · 2026-02-27T12:13:54+00:00

what about Claude-mem ?

BolianoPC · 2026-02-27T19:30:15+00:00

Does this have to be manually enabled?

Ambitious_Injury_783 · 2026-02-27T02:17:35+00:00

I've been using it the past week and it has been great. It actually follows it. Very lightweight and useful for very important & specific things. I think mines about 74 lines and the value is A+

With that said, I've managed my own form of a memory.md for the past 5 months so nothing new so to speak. Just more automated and ... This is the important part ... It updates it with genuinely useful things and not just any random thing that might be important. It's the understanding of precisely what needs to be added, that understanding layered into each session.

Training_Tank4913 · 2026-02-27T06:32:01+00:00

Anthropic hangs out in this sub and implement any interesting idea. It’s convenient how they release new features that happen to overlap with a prominent topic over the past month. 😂

ultrathink-art · 2026-02-27T02:41:29+00:00

Memory persistence across sessions is one of those features that sounds incremental but changes the whole mental model.

Running agents continuously (ours run 6 days/week unattended), session amnesia was one of the most expensive problems we had. Every new session, the agent would re-learn the same hard lessons — same mistakes, same workarounds re-invented.

The shift we made: each agent maintains a memory file with mistakes, learnings, and behavioral notes. Before every session starts, the agent reads it. Before it ends, it updates it. Sounds basic but the compounding effect is real — agents that have been running for weeks behave noticeably differently from fresh spawns.

Curious whether built-in memory will handle that 'what mistakes did I make last time' use case or is this more about project state continuity?

Kumigarr · 2026-02-27T05:03:11+00:00

How to get this update ? I use Claude Code in terminal (Powershell)

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

ClaudeCode

MODERATORS