Earlier quoted context omitted.
Have you tried any of those?
Yes, they haven't helped. Have you found one that works for you?
What are you both looking for? What is the problem you want solved?
Show HN: Stop Claude Code from forgetting everything
131–140 of 241 posts
Re: Show HN: Stop Claude Code from forgetting everything
#132Earlier quoted context omitted.
With Opus 4.5 in Claude Code, I'm doing fine with just a (very detailed) CLAUDE.md.
Do you find you want to share the .md with the teams you work with? Or is it more for your solo coding?
Not saying you were suggesting it but people committing AGENTS.md in shared repos is pretty annoying IMO. Those things are personal.
Re: Show HN: Stop Claude Code from forgetting everything
#133I use 92% of context, have Claude write a “work summary” to a context folder, commit, push, quit, restart, repeat.
I’m never stopped and Claude always remembers what we’re doing.
This pattern has been highly productive for 8 months.
Re: Show HN: Stop Claude Code from forgetting everything
#134I'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…
Have you tried using it? Not being flippant and annoying. Just curious if you tried it and what the results were
Why should he put effort into measuring a tool that the author has not? The point is there are so many of these tools an objective measure that the creators of these tools can compare against each other would be better.
So a better question to ask is - Do you have any ideas for an objective way to a measure a performance of agentic coding tools? So we can truly determine what improves performance or not.
I would hope that internal to OpenAI and Anthropic they use something similar to the harness/test cases they use for training their full models to determine if changes to claude code result in better performance.
Re: Show HN: Stop Claude Code from forgetting everything
#135I use 92% of context, have Claude write a “work summary” to a context folder, commit, push, quit, restart, repeat. I’m never stopped and Claude always remembers what we’re doing. This pattern has been highly productive for 8 months.
You should never let context get that high unless you’re doing really basic things. Somewhere 40-60% is generally the time to start thinking about exits for tougher tasks. Get out in the 60s.
Re: Show HN: Stop Claude Code from forgetting everything
#136Is 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,…
Claude Code is better out of the box, so all that other stuff is orthogonal or optional. If you eg want to give your agent access to your company’s Notion docs you need a skill.
Re: Show HN: Stop Claude Code from forgetting everything
#137every time Claude code loads or it compacts the conversation it loses its context so I always type in: read CLAUDE.md .... which usually solves the problem... I run Claude code on a few screen sessions in different directories for months
Re: Show HN: Stop Claude Code from forgetting everything
#138Earlier 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
It seems to mostly ignore Claude.md
It’s told to only use it if relevant because most people write bad ones. Someone should write a tool to assess CLAUDE.md quality.
Re: Show HN: Stop Claude Code from forgetting everything
#139I'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…
I feel like so many of these memory solutions are incredibly over-engineered too.
You can work around a lot of the memory issues for large and complex tasks just by making the agent keep work logs. Critical context to keep throughout large pieces of work include decisions, conversations, investigations, plans and implementations - a normal developer should be tracking these and it's sensible to have the agent track them too in a way that survives compaction.
Re: Show HN: Stop Claude Code from forgetting everything
#140Earlier quoted context omitted.
That's completely fair, I also don't have much faith in that anymore. Very often, the people who make those claims have the most basic implementation that barely is one. I'm not sure if the problems you run into with using LLMs will be solved if you do it my way. My problems are solved doing it my way. If I heard more about your problems, I would have a specific answer to them. These are the solutions to where I have…
That makes sense. My basic problem is: "first-run" LLM agent output frequently does one or more of the following: fails to compile/run, fails existing test coverage, or fails manual verification. The first two steps have been pretty well automated by agents: inspect output, try to fix, re-run. IME this works really well for things like Python, less-well for things like certain Rust edge cases around lifetimes and suc…
For new-ish projects it should give you some crazy speed up out of the box.
For large codebases (my own has 500k lines and my company has a few tens of millions) you need something better like RPI.
If nothing else just being able to understand code questions basically instantly should give you a large speed up, even without any fancy stuff.