Live data from Hacker News

Show HN: Stop Claude Code from forgetting everything

github.com

71–80 of 241 posts

Re: Show HN: Stop Claude Code from forgetting everything

#71
post #53

There are a quadrillion startups (mem0, langmem, zep, supermemory), open source repos (claude-mem, beads), and tools that do this. My approach is literally just a top-level, local, git version controlled memory system with 3 commands: - /handoff - End of session, capture into an inbox.md - /sync - Route inbox.md to custom organised markdown files - /engineering (or /projects, /tasks, /research) - Load context into ne…

The extention Cline has a "memory bank" feature. It's just a markdown you add as an instruction. Works well for me. Worked with agents.md as well so not just with the Cline extention. Pretty much the same idea.

Re: Show HN: Stop Claude Code from forgetting everything

#73

Is anyone else just completely overwhelmed with the number of things you _need_ for claude code? Agents, sub agents, skills, claud.md, agents.md, rules, hooks, etc. We use Cursor where I work and I find it a good medium for still being in control and knowing what is happening with all of the changes being reviewed in an IDE. Claude feels more like a black box, and one with so many options that it's just overwhelming,…

I'm in Claude Code 30+ hr/wk and always have a at least three tabs of CC agents open in my terminal. Agree with the other comments: pretty much running vanilla everything and only the Playwright MCP (IMO way better than the native chrome integration) and ccstatusline (for fun). Subagents can be as simple as saying "do X task(s) with subagent(s)". Skills are just self @-ing markdown files. Two of the most important th…

I also specifically instruct Claude how to use a globally git ignored scratch folder “tmp” in each repo. Curious what your approach is

Re: Show HN: Stop Claude Code from forgetting everything

#76
post #65

Earlier quoted context omitted.

I tend to agree with you, however compacting has gotten much worse. So... it's tough. I think memory abstractions are generally a mistake, and generally not needed, however I also think that compacting has gotten so wrong recently that they are also required until Claude Code releases a version with improved compacting. But I don't do memory abstraction like this at all. I use skills to manage plans, and the plans ar…

I’m interested to see your setup. I think planning is a critical part of the process. I just built https://github.com/backnotprop/plannotator for a simple UX enhancement Before planning mode I used to write plans to a folder with descriptive file names. A simple ls was a nice memory refresher for the agent.

I understand the use case for plannotator. I understand why you did it that way.

I am working alone. So I am instead having plans automatically update. Same conception, but without a human in the mix.

But I am utilizing skills heavily here. I also have a python script which manages how the LLM calls the plans so it's all deterministic. It happens the same way every time.

That's my big push right now. Every single thing I do, I try to make as much of it as deterministic as possible.

Re: Show HN: Stop Claude Code from forgetting everything

#77

This is impressive. Though I have found repo level claude.md that is updated everytime claude makes a mistake plus using —restore to select a previous relevant session works well. There is no way for Anthropic to optimize Claude code or the underlying models for these custom setups. So it’s probably better to stick with the patterns Anthropic engineers use internally.

Do you ever switch tools? I don't love the idea of my context being hostage of whatever LLM I choose first.

Re: Show HN: Stop Claude Code from forgetting everything

#79
I'm not sure how many HN users frequent other places related to agentic coding like the subreddits of particular providers, but this has got to be the 1000th "ultimate memory system"/break-free-of-the-context-limit-tyranny! project I've seen, and like all other similar projects there's never any evidence or even attempt at measuring any metric of performance improved by it. Of course it's hard to measure such a thing, but that's part of exactly why it's hard to build something like this. Here's user #1001 that's been told by Claude "What a fascinating idea! You've identified a real gap in the market for a simple database based memory system to extend agent memory."
Post reply on HN