New in v17.22.0 - ✨ Memory #2121
Replies: 3 comments 2 replies
-
This is awesome work @olimorris ! |
Beta Was this translation helpful? Give feedback.
-
Glad to see CodeCompanion evolve! I have read through the docs as you suggested but I still couldn't find the answers to these basic questions, perhaps this could be added to the docs?
I will play around with this now! :) PS. If i'm correct that this feature does not handle "adding to memory", do you have any plans on adding something corresponding to the parsers, eg. a inline slash command that shows a prompt and then calls a "serializer/memorize function" (mirroring the parser) that decides how to add it to memory? |
Beta Was this translation helpful? Give feedback.
-
Awesome! I've archived https://github.com/minusfive/codecompanion-agent-rules |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi All,
I'm pleased to share that in v17.22.0, I've added support for memory:
(not the most exciting video, unfortunately)
2025-09-14.00_20_13.-.WezTerm.mp4
Key points:
CLAUDE.md
file and adds it as context/memory
slash command to manually add aCodeCompanion/Chat
memory groupImportant
You will need to manually enable memory.
✨ Features
memory.opts.chat.default_memory
/memory
slash command to choose what memory to add to a chat bufferAs you're well aware, LLMs don’t retain memory between completions and it can be cumbersome to catch them up in new conversations. Back in January, I tackled this with workspaces. I stand by that idea and the principle. In fact, workspaces are probably the feature I use most in CodeCompanion.
Alas, in their current form, I just feel workspaces being one long JSON file is not conducive to developer happiness.
In #1718, @arnm was kind enough to share his implementation of rules. That is, the rules, files and guidelines that are project specific and useful for sharing with every request to the LLM. With the rise of agents like Claude Code, we have new context files like
CLAUDE.md
that I expect you're all familiar with.@arnm's work very much inspired me to think deeply about how CodeCompanion could better support developers who work across multiple projects and as part of large teams.
I strongly advise reading about how you can configure memory to get the most out of it. I expect a lot of initial questions can be answered by perusing that page.
Finally, I'm expecting to remove workspaces from the plugin entirely once we get to v18.0.0. But not expecting that to be anytime in the near future.
Thanks and hope you enjoy as much as I do.
Now on to fixing some Claude Code bugs...
Oli
Beta Was this translation helpful? Give feedback.
All reactions