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

211–220 of 241 posts

Re: Show HN: Stop Claude Code from forgetting everything

#211

Post by ramoz »

hasperdi wrote: post #180
ramoz wrote: post #143

Earlier quoted context omitted.

Great advise. For large plans I tell the agent to write to an “implementation_log.md” and make note of it during compaction. Additionally the agent can also just reference the original session logs.

The problem with this approach, is that the model may forget to update the log... It usually happens when the context window >50% filled

I found this happen less often if the task is a part of the plan. It typically gets in a cycle habit of editing code and updating the doc

Re: Show HN: Stop Claude Code from forgetting everything

#213

Post by ramoz »

christinetyip wrote: post #201
saberience wrote: post #193

Do we really need another vibe-coded LLM context/memory startup? Do the authors have any benchmarks or test to show that this genuinely improved outputs? I have tried probably 10-20 other open source projects and closed source projects purporting to improve Claude Code with memory/context, and still to this date, nothing works better than simply keeping my own library of markdown files for each project specification,…

I mostly agree with this, if the goal were “better persistent memory inside Claude Code,” that wouldn’t be very interesting. For a single agent and a single tool, keeping project specs and decisions in markdown and explicitly pointing the model at them works well. We do that too. What we’re focused on is a different boundary: memory that isn’t owned by a specific agent or tool. Once you start switching between tools…

If markdown in a git repository isn’t good enough for collaboration, then why would any plugged in abstraction be better?

You imply you have a solution for current wholistic state. For this you would need a solution for context decay and relevant curation — with benchmarks that prove it is also more valuable than constant rediscovery (for quality and cost).

That narrative becomes harsher once you pivot to “general purpose agents” because you’re then competing with every existing knowledge work platform. So you’ll shift into “unified context for all your KW platforms” - where presumably the agents already have access (Claude today can basically go scrape all knowledge from anywhere).

So then it becomes an offering of “current state” in complex human processes and this is a concept I’m not sure any technology can capture; whether it’s across codebases (which for humans we settled on git) and especially not general working scenarios. And I guess this is where it becomes a unified multi-agent wholistic state capture. Ambitious and fun problem.

Re: Show HN: Stop Claude Code from forgetting everything

#214

Post by edmundsauto »

AndyNemmity wrote: post #76
ramoz wrote: post #65

Earlier quoted context omitted.

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

Would you share an overview of how it works? Sounds interesting

Re: Show HN: Stop Claude Code from forgetting everything

#215

Post by AndyNemmity »

troupo wrote: post #172
AndyNemmity wrote: post #106

Earlier quoted context omitted.

The funny part is, the vast majority of them are barely doing anything at all. All of these systems are for managing context. You can generally tell which ones are actually doing something if they are using skills, with programs in them. Because then, you're actually attaching some sort of feature to the system. Otherwise, you're just feeding in different prompts and steps, which can add some value, but okay, it does…

> You can generally tell which ones are actually doing something if they are using skills, with programs in them. > Otherwise, you're just feeding in different prompts and steps "skills" are literally just .md files with different prompts and steps. > That's actually adding something claude code doesn't have, instead of just saying "You are an expert in blah" It's not adding anything but a prompt saying "when asked t…

Skill are md files, but they are not just that. They are also scripts. That's what adding things are. You can make a skill that is just a prompt, but that misses the point of the value.

You're packaging the tool with the skill, or multiple tools to do a single thing.

Re: Show HN: Stop Claude Code from forgetting everything

#216

Post by AndyNemmity »

dnautics wrote: post #188
AndyNemmity wrote: post #91

Earlier quoted context omitted.

So MCPs are a bunch of, essenntially skill type objects. But it has to tell you about all of them, and information about all of them up front. So a Skill is just a smaller granulatrity level of that concept. It's just one of the individual things an MCP can do. This is about context management at some level. When you need to do a single thing within that full list of potential things, you don't need the instructions…

no that makes no sense. the skill doesn't do anything by itself, the mcp (can be) attached to a deterministic oracle that can return correct information.

But the skill includes the scripts to do things.

So in my nano banana image generation skill, it contains a python script that does all the actual work. The skill just knows how to call the python script.

We're attaching tools to the md files. This is at the granular level of how to hammer a nail, how to use a screw driver, etc. And then the agent, the handyman, has his tool box of skills to call depending on what he needs.

Re: Show HN: Stop Claude Code from forgetting everything

#217

Post by AndyNemmity »

dnautics wrote: post #191
austinbaggio wrote: post #108

Earlier quoted context omitted.

In our experience, a lot of it is feel and dev preference. After talking to quite a few developers, we've found the skill was the easiest to get started with, but we also have a CLI tool and an MCP server too. You can check out the docs if you'd prefer to try those - feedback welcome: https://www.ensue-network.ai/docs#cli-tool

yeah but a skill without the mcp server is just going to be super inefficient at certain things. again going to my example, a skill to do a dependency graph would have to do a complex search. and in some languages the dependency might be hidden by macros/reflection etc which would obscure a result obtained by grep how would you do this with a skill, which is just a text file nudging the llm whereas the MCP's server g…

A skill is not just a text file nudging the llm. You group scripts and programming to the skill, and the skill calls it.

Re: Show HN: Stop Claude Code from forgetting everything

#218

Post by AndyNemmity »

edmundsauto wrote: post #214
AndyNemmity wrote: post #76

Earlier quoted context omitted.

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

Would you share an overview of how it works? Sounds interesting

Perhaps I can release it as a standalone github skill, and then do a blog post on it or something.

I'm just also working on real projects as well, so a lot of my priority is focused on new skills building, and not worrying about managing the current ones I have as github repos.

Re: Show HN: Stop Claude Code from forgetting everything

#219

Post by hasperdi »

ramoz wrote: post #211
hasperdi wrote: post #180

Earlier quoted context omitted.

The problem with this approach, is that the model may forget to update the log... It usually happens when the context window >50% filled

I found this happen less often if the task is a part of the plan. It typically gets in a cycle habit of editing code and updating the doc

thanks, I'll keep that in mind

Re: Show HN: Stop Claude Code from forgetting everything

#220

Post by [deleted] »

austinbaggio wrote: post #120
ec109685 wrote: post #70

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.

If you give it a try, I think that use case should work, but if not, I would be grateful if you told us what broke. And also - I genuinely worry about vendor lock-in, do you?

[deleted]
Post reply on HN