Live data from Hacker News

Show HN: Stop Claude Code from forgetting everything

github.com

81–90 of 241 posts

Re: Show HN: Stop Claude Code from forgetting everything

#81
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

It seems to mostly ignore Claude.md

If you can test how often it is being used by having a line in there saying something like “You must start every non-code response with ‘Woohoo!’”

Re: Show HN: Stop Claude Code from forgetting everything

#82
The past few weeks I've been experimenting with using less context and less memory and it's been going really well. Where before I'd try to do a bunch of fairly related things in a single session, experimenting with compacting more or less frequently, now I'm clearing my context or exiting and restarting claude and codex. It seems to help it focus on the task at hand, hasn't tended to go off into the weeds as much, and my token costs have dropped way down.

Combined with a good AGENTS.md, it seems to be working really well.

Re: Show HN: Stop Claude Code from forgetting everything

#84

The past few weeks I've been experimenting with using less context and less memory and it's been going really well. Where before I'd try to do a bunch of fairly related things in a single session, experimenting with compacting more or less frequently, now I'm clearing my context or exiting and restarting claude and codex. It seems to help it focus on the task at hand, hasn't tended to go off into the weeds as much, a…

That’s been my experience as well. I find I usually get better output if I create a new conversation for each thing I need. I’ve found that the only times it’s better to continue an existing conversation is if I want to have it make small improvements or changes to something it just wrote, as it tends to do better with the previous context still there. But even that only goes so far, then the scale tips and it works much better with a clean slate. I especially don’t want totally unrelated conversations polluting the context which is why I have all memory features turned off in all the web chat UI’s for the models I use.

Re: Show HN: Stop Claude Code from forgetting everything

#86

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 use both Cursor and Claude Code in VS Code at work (so I get similar control as Cursor). I don’t really use Claude Code any differently than cursor. People way over complicate it.

Re: Show HN: Stop Claude Code from forgetting everything

#87

I don't understand the use case. I think if you don't use agents, and skills currently effectively, then perhaps this is useful. If you're using them though, we no longer have the problem of Claude forgetting things.

I'm curious how those replace this? I've barely used either, and would love to hear more.

Re: Show HN: Stop Claude Code from forgetting everything

#88

Earlier quoted context omitted.

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.

i don't understand this mcp/skill distinction? one of the mcps i use indexes the runtime dependency of code modules so that claude can refactor without just blindly grepping.

how would that be a "skill"? just wrap the mcp in a cli?

fwiw this may be a skill issue, pun intended, but i can't seem to get claude to trigger skills, whereas it reaches for mcps more... i wonder if im missing something. I'm plenty productive in claude though.

Re: Show HN: Stop Claude Code from forgetting everything

#90
post #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…

Which of the 1000 is your favorite? There does seem to be a shallow race to optimizing xyz benchmark for some narrow sliver of the context problem, but you're right, context problem space is big, so I don't think we'll hurry to join that narrow race.
Post reply on HN