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

Show HN: Stop Claude Code from forgetting everything

github.com

Post reply on HN
Print view View original

61–70 of 241 posts

Re: Show HN: Stop Claude Code from forgetting everything

#61

Post by AndyNemmity »

ramoz wrote: post #60
AndyNemmity wrote: post #49

Earlier quoted context omitted.

There is certainly a level where at any time you could be building some abstraction that is no longer required in a month, or 3. I feel that way too. I have a lot of these things. But the reality is, it doesn't really happen that often in my actual experience. Everyone is very slow as a whole to understand what these things mean, so far you get quite a bit of time just with an improved, customized system of your own.

My somewhat naive heuristic would be that memory abstractions are a complete mistep in terms of optimization. There is no "super claude mem" or "continual claude" until there actually is. https://backnotprop.com/blog/50-first-dates-with-mr-meeseeks...

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 are the memory abstraction.

But that is more than memory. That is also about having a detailed set of things that must occur.

Re: Show HN: Stop Claude Code from forgetting everything

#62

Post by lobito25 »

wouldbecouldbe wrote: post #31
JoshGlazebrook wrote: post #18

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

All I use is curse words and it does a damn great job most of the time

Same here :)))), he's really good at understanding when you're pissed off.

Re: Show HN: Stop Claude Code from forgetting everything

#64

Post by AndyNemmity »

ossa-ma wrote: 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…

Your approach essentially matches mine, but I call them plans. I agree with you that the other tools don't seem to add any value compared to this structure.

I think at this point in time, we both have it right.

Re: Show HN: Stop Claude Code from forgetting everything

#65

Post by ramoz »

AndyNemmity wrote: post #61
ramoz wrote: post #60

Earlier quoted context omitted.

My somewhat naive heuristic would be that memory abstractions are a complete mistep in terms of optimization. There is no "super claude mem" or "continual claude" until there actually is. https://backnotprop.com/blog/50-first-dates-with-mr-meeseeks...

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.

Re: Show HN: Stop Claude Code from forgetting everything

#66

Post by AndyNemmity »

parpfish wrote: post #54
asdev wrote: post #20

Earlier quoted context omitted.

you really don't need any of this crap. you just need Claude Code and CLAUDE.MD in directories where you need to direct it. complicated AI set ups are mid curve

I refuse to learn all the complicated configuration because none of it will matter when they drop the next model. Things that need special settings now won’t in the future and vice versa. It’s not worth investing a bunch of time into learning features and prompting tricks that will be obsoleted soon

I wish that were true. Models don't feel like they've really had massive leaps.

They do get better, but not enough to change any of the configuration I have.

But you are correct, there is a real possibility that the time invested with be obsolete at some point.

For sure the work towards MCPs are basically obsolete via skills. These things happen.

Re: Show HN: Stop Claude Code from forgetting everything

#67

Post by ec109685 »

austinbaggio wrote: post #42
senshan wrote: post #7

What is the advantage over summarizing previous sessions for the new one? Or, over continuing the same session and compacting?

You can use it with summaries for sure, but summaries often miss edge cases and long sessions drift. This makes it easier to jump between tasks, come back days later, and reorient without missing something that the summarization or compaction might have gotten rid of. I've often found post-compaction, the memory of even the current session feels so much dumber.

You can go to a previous session and resume from there. Plus keep updating the repo claude.md along the way:

Re: Show HN: Stop Claude Code from forgetting everything

#68

Post by austinbaggio »

JoshGlazebrook wrote: post #18

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

It is overwhelming. We have support for Cursor mcp as well, but you lose a lot of the auto-magic stuff you get with the Claude Code plugin. Unfortunately, skills are pretty sticky to the Claude Code stack. It is kind of the vim of AI coding agents. . . One of the goals for this tool was to address context management in a single place. i.e instead of setting up all of the rules, claude.md, and skill.md you just semantic query a specific namespace in your knowledge base.

the docs if you are curious: https://www.ensue-network.ai/docs

Re: Show HN: Stop Claude Code from forgetting everything

#70

Post by ec109685 »

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.

Post reply on HN