Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Recall – Local project memory for Claude Code

github.com

Post reply on HN
Print view View original

31–40 of 96 posts

Re: Show HN: Recall – Local project memory for Claude Code

#31

Post by devmor »

petee wrote: post #20
giancarlostoro wrote: post #3

I never have to because I use a ticketing system the model goes through in addition to a CLAUDE.md file with a summary, including vision, goals, non-goals etc

Any tricks to get Claude to actually use the CLAUDE.md consistently? Many times now its completely ignored it, despite being short, concise + generated by Claude itself, and I see bug reports about this that are over a year old

Check out your session logs and review what is actually in the context window. I’m willing to bet that your CLAUDE.md is sitting close to the middle of everything in there. The current gen of frontier models tends to heavily weight the start and end of the current context so heavily that anything partway through may just be ignored.

Re: Show HN: Recall – Local project memory for Claude Code

#32

Post by drivebyhooting »

iwontberude wrote: post #28
drivebyhooting wrote: post #24

Why 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

Compaction already drops nuanced and salient information. I wouldn’t want any additional amnesia from overly simplistic summarization.

Re: Show HN: Recall – Local project memory for Claude Code

#33

Post by mikeocool »

I apparently use Claude differently the most people who talk about using Claude on the internet.

I’ll typically have a bunch of short sessions over the course of a day. Anytime I start a task that isn’t going to very directly benefit from the existing context I start fresh.

I don’t find a lot of benefit in explaining the project overall to Claude — I’ve deleted a lot of that explanation from my Claude.md because it didn’t seem to impact much.

I typically start a task by pointing it to 1-2 files and giving it some explanation of what I want done, and it figures it out.

Basically never hit context window limits or compactions, and can’t remember the last time I hit a 5 hour or a weekly limit.

Re: Show HN: Recall – Local project memory for Claude Code

#34

Post by airstrike »

serial_dev wrote: post #13

I 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?

Depending on the scale of the project and the complexity of the specific thing you need to work on, it's advantageous to bring specific context into the session instead of hoping the model will connect the right dots.

Re: Show HN: Recall – Local project memory for Claude Code

#35

Post by airstrike »

chatmasta wrote: post #29
suprjami wrote: post #25

Earlier quoted context omitted.

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…

It's funny because with so many different implementations of /handoff, I wonder if anyone has benchmarked handoff-and-resume to figure out what the best performance implementation looks like.

I also imagine that varies by model.

Re: Show HN: Recall – Local project memory for Claude Code

#36

Post by torben-friis »

serial_dev wrote: post #13

I 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?

I guess that depends on the kind of project, how common the intent is, how self contained, etc.

Re: Show HN: Recall – Local project memory for Claude Code

#38

Post by [deleted] »

chatmasta wrote: post #29
suprjami wrote: post #25

Earlier quoted context omitted.

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…

[deleted]
Post reply on HN