How is this different than just using a resume?
Show HN: Recall – Local project memory for Claude Code
21–30 of 96 posts
Re: Show HN: Recall – Local project memory for Claude Code
#22CLAUDE.md is already a good system for context window management for all the same reasons that version control management of code is good.
And keeping a local copy of everything you ever told Claude in your context window is bad for the same reasons keeping a local copy of your code called My_Code_v3_final.zip is bad.
Re: Show HN: Recall – Local project memory for Claude Code
#23Are there any benchmarks/evals to back the claims? Or how do you know that it helps reducing waste?
They don’t. It’s all based on FOMO. Like superpowers, the more the better.
My advice: the best claude is the raw claude, with some custom tailored skills. That’s it, no plugins.
Re: Show HN: Recall – Local project memory for Claude Code
#24Why would you want a simple summarizer instead of frontier AI doing the summarization for you?
Re: Show HN: Recall – Local project memory for Claude Code
#25I might be missing out on something but I never had to explain my project. Just give it a task, or if you really want to, type it quickly, then you are good to go. I can’t imagine this being worth optimizing. The issue is never that Claude can’t figure out what the projects is about… Am I missing something or does this project not solve a problem most regular people have?
There are many other posts here which agree with you. Filling context with what you think the model needs adds nothing and possibly just inflates context which is harmful.
A good method seems to be only make a skill or memory when the LLM gets something wrong, or if you actually observe it's always doing the same step and you can get the model to the same place with less tokens.
Re: Show HN: Recall – Local project memory for Claude Code
#26Exciting to see hooks used for automation.
But if I may, the need to manually update the context is a huge hurdle.
Automation like this is limited unless no human has to remember it. So perhaps you can save context during the PreCompact and Stop hooks.
Re: Show HN: Recall – Local project memory for Claude Code
#27I think the majority here have stated the same... That CLAUDE.md or AGENTS.md effectively do this. Either that or the readme.
The only tip I can give is that your skill that builds or wraps up work. You should have it update those files if anything has changed.
Claude/Agents files shouldn't be bloated, but should imho act as a basic amount of context on the project so your agent and skills can pick up and go, with even the most basic initial prompt.
Re: Show HN: Recall – Local project memory for Claude Code
#28Why would you want a simple summarizer instead of frontier AI doing the summarization for you?
Bc frontier models are expensive and summarization is basic af
Re: Show HN: Recall – Local project memory for Claude Code
#29I might be missing out on something but I never had to explain my project. Just give it a task, or if you really want to, type it quickly, then you are good to go. I can’t imagine this being worth optimizing. The issue is never that Claude can’t figure out what the projects is about… Am I missing something or does this project not solve a problem most regular people have?
There are many other posts here which agree with you. Filling context with what you think the model needs adds nothing and possibly just inflates context which is harmful. A good method seems to be only make a skill or memory when the LLM gets something wrong, or if you actually observe it's always doing the same step and you can get the model to the same place with less tokens.
I’ve basically never edited a skill or memory myself. I make the LLM do it as part of the /handoff skill before I clear a session. That also includes pruning existing skills/memories and resolving any drift.
Even the /handoff skill was written by the model…
Re: Show HN: Recall – Local project memory for Claude Code
#30I think the majority here have stated the same... That CLAUDE.md or AGENTS.md effectively do this. Either that or the readme. The only tip I can give is that your skill that builds or wraps up work. You should have it update those files if anything has changed. Claude/Agents files shouldn't be bloated, but should imho act as a basic amount of context on the project so your agent and skills can pick up and go, with ev…
> The only tip I can give is that your skill that builds or wraps up work. You should have it update those files if anything has changed.
Depending on the scope of work you’re doing, it might be better to have this removed from the context of the work that was done.
I keep a “Last Updated Hash” in my md and every so often will have the LLM pull a diff from that hash to the current head, then determine what doesn’t match.