elfenleid

5 ms·

1.
Show HN: Recall – Persistent Memory for Claude Code via MCP Hooks(recallmcp.com)
1 points by elfenleid 7mo ago|0 comments
2.
by elfenleid 1y ago
I've been experimenting with that in the last couple of days. I added to CLAUDE.md a directive on how and when to use recall and he's autoamtically calling the tool for store and fetch
3.
by elfenleid 1y ago
Absolutely! But this is not a replacement of those files, this is a different (better?) way to navigate through those learnings instead of having to read whole files.
4.
by elfenleid 1y ago
Hey! You're mixing up two different things: 1. Claude Desktop's built-in `/memory` command (what you tried) - just lists CLAUDE.md files 2. Recall MCP server (this project) - completely separate tool you need to install Recal
5.
by elfenleid 1y ago
The other point here, I wanted something more in line with LLMs natural language, something that can be queried more effeciently buy just using normal language, almost like the way we think normally, we first have a though and then we go th
6.
by elfenleid 1y ago
Let me have a look, thanks for reporting that. This is very much in development and I keep adding features to it. Any suggestions let me know. The way I use it, I add instructions to CLAUDE.md on how I want him to use recall, and when. ## U
7.
by elfenleid 1y ago
Absolutely. Remember these are just tools, how each one of us uses them it's a diffrent story. A lot can be leveraged as well by adding a couple of lines to CLAUDE.md on how he should use this memory solution, or not, it's totally
8.
by elfenleid 1y ago
No particular specific reason. I was working with another project that also had redis and decided to start with it. It can be changed to other tool, which one would you recommend?
9.
by elfenleid 1y ago
I think that's a great point. I will experiment with different approaches. I started with redis mostly because it's something I have experience with and was a quick setup win, but having different strategies I think it could make
10.
by elfenleid 1y ago
I think that's a great point really. There is not 1 size fits all, different people will have different strategies that better suit their workflow.
11.
by elfenleid 1y ago
Totally, point taken. I'll dig a bit deeper into that.
12.
by elfenleid 1y ago
Yeah that's a solid workflow and honestly simpler than what I built - I think Recall makes sense when you hit the scale where managing multiple .md files becomes tedious (like 50+ conversations across 10 projects), but you're righ
13.
by elfenleid 1y ago
Yeah people do that but it doesn't scale, after a while your "restart prompt" is 50KB and won't fit, plus you're stuck copying stuff manually instead of just asking "what did we say about Redis" and gettin
14.
by elfenleid 1y ago
Yeah it still uses context but way more efficiently, instead of injecting a 50KB context.md every time, Recall searches 10k memories and only injects the top 5 relevant ones (maybe 2KB), so you can store way more total knowledge.
15.
by elfenleid 1y ago
Yep! Valkey should work fine. Recall just uses basic Redis commands - HSET, SADD, ZADD, etc. Nothing fancy. Valkey is Redis-compatible so all those commands work the same. I haven't tested it personally but there's no reason it wo
16.
by elfenleid 1y ago
That's a great point! And also works really well for shared context between claude instances, for example, we use that for our business model in the company, all business rules and model is stored as memories in a central redis that th
17.
by elfenleid 1y ago
I've been using it for a while now, personally. I've found that I have less issues with context, I can easily recall (pun intended) after a context compact, etc.
18.
by elfenleid 1y ago
Totally get what you're saying! Having Claude manually call memory tools mid-conversation does feel intrusive, I agree with that, especially since you need to keep saying Yes to the tool access. Your approach is actually really interes
19.
by elfenleid 1y ago
Yes I did, I worked on this a while back, before it was availabale I believe. I'll have another check. Thanks for the heads up
20.
by elfenleid 1y ago
I still do, but having this allows for strategies like memory decay for older information. It also allows for much more structured searching capabilities, instead of opening file which are less structured. .md files work great for small pro
21.
by elfenleid 1y ago
That's a great point, the reality is that context, at least from personal experience, is brittle and over time will start to lose precision. This is a always there, persistent way for claude to access "memories". I've be
22.
Show HN: Recall: Give Claude memory with Redis-backed persistent context(npmjs.com)
171 points by elfenleid 1y ago|93 comments