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

81–90 of 96 posts

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

#81

Post by catlifeonmars »

bfeynman wrote: post #63
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?

What I've finally come to understand is that there is a large amount of people who are now able to write and use software through claude and coding agents. Those people have different needs than more traditional software engineers who have more knowledge because even best llms often need steering, correction, and refactoring suggestions when iterating on code and it's fine to let it lose context because exactly like…

Git commit?

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

#82

Post by chatmasta »

airstrike wrote: post #35
chatmasta wrote: post #29

Earlier quoted context omitted.

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.

Mine are project-specific, which is a bit annoying since I’d like it to be global but there are some project-specific additions. Maybe I’ll (ask Claude to) refactor that to be more composable.

It should be a first class feature of the harness, tbh. It kind of is with the /compact [focus] parameter but this is coarse and leaves no record. I find keeping the handoff files in the repo to be useful for historical context and later debugging.

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

#83

Post by theshrike79 »

whalesalad wrote: post #49
mikeocool wrote: post #33

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 d…

Honestly sounds like you’re not doing anything difficult. If I’m doing easy tasks it’s fine but if you need to do a major architectural project that spans 3 codebases and 2 clouds you’re gonna have a hard time without substantial context/memory management.

But that's an anomaly. I'm pretty sure you're not doing major architectural changes over 3 codebases and 2 clouds daily?

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

#84

Post by theshrike79 »

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 specifically have instructions for claude explaining the purpose of the project in pretty much all repos. Just a simple PROJECT.md is enough - and referenced from AGENTS.md

There I usually lay out stuff like "this is a personal greenfield project" and "don't bother with multi-user support" etc. Or Claude will default to creating something WEBSCALE for a simple tool that won't run outside of my local LAN-only Proxmox setup. And that'll also skip massive database migration support for a project that's 3 days old - the agent doesn't know that. I'm just dropping it on the project after a full memory wipe.

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

#86

Post by computerex »

nibbleyou wrote: post #76
computerex wrote: post #54

Earlier quoted context omitted.

I work in a completely different manner. I have a chief of staff agent, which is one Claude code instance that orchestrates work across all my projects simultaneously with sub agents. In this way the agent helps me context switch and drive work towards everything I’m working on. I only use 1 session, I compact when necessary with todos and on file system files to track wip

Mind sharing details of your setup?

It's very simple. I have told Claude that it's my chief of staff and that it must delegate all tasks to subagents. That as my COS it must show initiative and only come to me for vision/decision making. I have hooks further enforcing this. It works really well because I am usually working on like 12 things at once. Feels like playing simultaneous chess. The COS agent helps me context switch/orchestrate everything. Subagents have their own context window so the COS context does not get polluted/filled up with low level subtask details. COS can effectively prompt the subagents. My main session does grow and I compact it from time to time. But since all the WIP is already captured in external state, compaction of the main session does not degrade performance.

I have used this same pattern in my own harness and it works well there too. https://github.com/computerex/z

I hooked an instance of my harness up to telegram and now I talk to it from everywhere it and dispatches work out to subagents.

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

#87

Post by whalesalad »

theshrike79 wrote: post #83
whalesalad wrote: post #49

Earlier quoted context omitted.

Honestly sounds like you’re not doing anything difficult. If I’m doing easy tasks it’s fine but if you need to do a major architectural project that spans 3 codebases and 2 clouds you’re gonna have a hard time without substantial context/memory management.

But that's an anomaly. I'm pretty sure you're not doing major architectural changes over 3 codebases and 2 clouds daily?

you'd be surprised.

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

#88

Post by juhnu85 »

I have had a computer completely get fried when working on something. I did lose the project memory with Claude. Even when everything was in GitHub and was working in OneDrive it still took some time to get Claude up to speed on a second PC. Could see this being helpful.

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

#90

Post by avihashu »

anecdotal but in my last from-scratch project claude code seemed to pick up on a lot of nuance on its own — conventions, prior decisions, stuff i didn't explicitly restate — without me feeding it back in. makes me wonder how much of this gap is already closing on agent side vs needing a dedicated tool like this
Post reply on HN