Live data from Hacker News

Show HN: Recall – Local project memory for Claude Code

github.com

91–96 of 96 posts

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

#91
Somewhat related, I built ccrider [1], which indexes the session transcripts that agents already write to disk (Claude Code, Codex, Copilot) into a local SQLite FTS database. It has a TUI, CLI, and an MCP server so the agent can search past sessions itself. Same local-first idea, based the raw logs rather than a maintained digest. Should work nicely with recall as well.

[1] https://github.com/neilberkman/ccrider

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

#92

I use Deepseek and just as it to generate a state.md file with a summary of the project every time I've reached a goal or milestone. I then take a few minutes to edit this and add in or take out details. Between token pricing and generous cache discounts This has proved very efficient so far, I reset every few hours of work and bypass the muddle of having too many priorities or over-extrapolation from un-nuanced inst…

> But while it would make a great recording of project history, I wonder if a lot of it doesn't end up detailing blind alleys the project went down and had to back out of

Yes, I've run into this as well. I had the agent document the changes it would make along the way, but it would want to keep making note of things that we switched away from. Eg, "In phase3 we used mysql instead of sqlite". On some projects I let the agwnt do all the documentation and plan.md and state.md files, and every so often go through manually and delete some of the cruft that's no longer needed.

Post reply on HN