4 ms·
If you look at the changelog[0] for 2.0, it doesn't mention any memory features. I also find it strange that they released this as 2.0 without any new actual Cl
by koakuma-chan 1y ago
If you look at the changelog[0] for 2.0, it doesn't mention any memory features. I also find it strange that they released this as 2.0 without any new actual Claude Code features other than /rewind, which I'm not sure what is for, since we already have version control.
[0]: https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md#200 https://github.com/anthropics/claude-code/blob/main/CHANGELO...
- steveklabnik 1y agoSo, when Anthropic had that huge release day, with Sonnet 4.5, Code 2.0, etc, this was one of the things they published: https://www.anthropic.com/news/context-management https://www.anthropic.com/news/context-management > The memory tool enables Claude to store and consult information outside the context window through a file-based system. Claude can create, read, update, and delete files in a dedicated memory directory stored in your infrastructure that persists across conversations. This allows agents to build up knowledge bases over time, maintain project state across sessions, and reference previous learnings without having to keep everything in context. This is what made me think that it came out with the 2.0.0 release. But apparently /memory landed in 1.0.94. Frustrating!
- koakuma-chan 1y agoFWIW, you can instruct it to edit CLAUDE.md on its own. At this point I am too lazy to type myself, so I never used /memory (which just appends to CLAUDE.md). The problem though is that it gets bloated and hard-to-read pretty quickly, and I forget what exactly I put in there.
- steveklabnik 1y agoYeah previously it had # to make that easy. But I also worry about CLAUDE.md bloat and so don't tend to continually update it.
- koakuma-chan 1y agoOh yeah # is actually what I meant.