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

201–210 of 241 posts

Re: Show HN: Stop Claude Code from forgetting everything

#201

Post by christinetyip »

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 (Claude, Codex, Cursor, etc.), or running multiple agents in parallel, markdown stops being “the memory” and becomes a coordination mechanism you have to keep in sync manually. Context created in one place doesn’t naturally flow to another, and you end up re-establishing state rather than accumulating it.

That’s why we're not thinking about this as "improving Claude Code”. We’re interested in the layer above that: a shared, external memory that can be plugged into any other model and tools, that any agent can read from or write to, and that can be selectively shared with collaborators. Context created in Claude can be reused in Codex, Manus, Cursor, or other agents from collaborators - and vice versa.

If one already built and is using one agent in one tool and is happy with markdown, they probably don’t need this. The value shows up once agents are treated as interchangeable workers and context needs to move across tools and people without being re-explained each time.

Re: Show HN: Stop Claude Code from forgetting everything

#202

Post by d4rkp4ttern »

I like that it does not require following any particular "system" or discipline. But having to use a non-local/proprietary memory layer is not ideal.

My own fully-local, minimalistic take on this problem of "session continuation without compaction" is to rely on the session JSONL files directly rather than create separate "memory" artifacts, and seamlessly index them to enable fast full-text search. This is the idea behind the "aichat" command-group + plugin I just added to my claude-code-tools [1] repo. You can quit your Claude-Code/Codex-CLI session S and type

    aichat resume
It launches a TUI, offering a few ways to continue your work:

- blind trim - clones the session, truncates large tool calls/results and older assistant messages, which can clear up as much as 50% of context depending of course on what's going on; this is a quick hack to continue your work a bit longer

- smart trim - similar but uses headless agent to decide what to truncate

- rollover: the one I use most frequently; it creates a new session S1 (which can optionally be a different CLI agent, allowing cross-agent work continuation), and injects back-pointers to the parent session JSONL file of S, the parent's parent , and so on (what I call session lineage) , into the first user message, and the user can then prompt the agent to use a sub-agent to extract arbitrary context from the ancestor sessions to continue the work.

[1] https://github.com/pchalasani/claude-code-tools?tab=readme-o...

Re: Show HN: Stop Claude Code from forgetting everything

#203

Post by christinetyip »

AndyNemmity wrote: post #34

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.

That makes sense, and I agree that for a single agent using skills well, Claude’s native context handling has gotten much better.

This wasn't mentioned in the first post, but the use case we’re focused on isn’t really “Claude forgetting,” but context living beyond a single agent or tool. Even if Claude remembers well within a session, that context is still owned by that agent instance.

The friction shows up when you switch tools or models (Claude → Codex / Cursor / etc.), run multiple agents in parallel, or want context created in one place to be reused elsewhere without re-establishing it.

In those cases, the problem isn’t forgetting so much as fragmentation. If someone is happy with one agent and one tool, there are probably a bunch of memory solutions to choose from. The value of this external memory network that you can plug into any model or agent shows up once context needs to move across tools and people.

Re: Show HN: Stop Claude Code from forgetting everything

#204

Post by gbnwl »

christinetyip wrote: post #200
gbnwl wrote: post #197

Earlier quoted context omitted.

> That’s the part that’s hard (or impossible) to do with markdown files or tool-local memory. I'm confused because every single thing in that list is trivial? Why would Codex have trouble reading a markdown file Claude wrote or vice versa? Why would multiple agents need their own copy of the markdown file instead of just referring to it as needed? Why would it be hard to share specific files with teammates or collabo…

You’re right that reading the same markdown file is trivial, that’s not the hard part. Where it stopped being trivial for us was once multiple agents were working at the same time. For example, one agent is deciding on an architecture while another is already generating code. A constraint changes mid-way. With a flat file, both agents can read it, but you’re relying on humans as the coordination layer: deciding which…

You're still not closing the gap between the problems you're naming and how your solution solves them?

> With a flat file, both agents can read it, but you’re relying on humans as the coordination layer: deciding which docs are authoritative, when plans are superseded, which tickets are still valid, and how context should be scoped for a given agent.

So the memory system also automates project management by removing "humans as the coordination layer"? From the OP the only details we got were

"What it does: (1) persists context between sessions (2) semantic & temportal search (not just string grep)"

Which are fine, but neither it nor you explain how it can solve any of these broader problems you bring up:

"deciding which docs are authoritative, when plans are superseded, which tickets are still valid, and how context should be scoped for a given agent, questions like who can read vs. update which parts of context, how to share only relevant decisions, how agents discover what matters without scanning a growing pile of files, and how updates propagate without state drifting apart."

You're claiming that semantic and temporal search has solved all of this for free? This project was presented as a memory solution and now it seems like you're saying its actually an agent orchestration framework, but the gap between what you're claiming your system can achieve and how you claim it works seems vast.

Re: Show HN: Stop Claude Code from forgetting everything

#205

Post by ryanthedev »

beefsack wrote: post #139
gbnwl wrote: 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…

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

I agree. Plan files and I use git for my work logs. Have been successful.

Re: Show HN: Stop Claude Code from forgetting everything

#208

Post by DrewADesign »

johnnyfived wrote: post #150
gbnwl wrote: post #147

Earlier quoted context omitted.

I think maybe the point they were trying to make is that despite people on HN being very technically experienced, skepticism and distrust of LLM-assisted coding tools may have prevented many of them from exploring the space too deeply yet. So a project like this may seem novel to many readers here, when the reality for users who've been using and following tools like Claude Code (and similar) closely for a while now…

They pretty much perfectly encapsulated the point in their fired up response haha.

Ha — so it seems… so it seems…

Re: Show HN: Stop Claude Code from forgetting everything

#209

Post by floatrock »

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

right. I stopped reading at "ENSUE_API_KEY | Required. Get one at [dashboard](link to startup showing this is an ad)"

First thought: why do I need an API key for what can be local markdown files. Make contents of CLAUDE.md be "Refer to ROBOTS.md" and you've got yourself a multi-model solution.

Main objection to corporate AI uptake is what are you gonna do with our data. The value prop over local markdown files here is not at all clear to even begin asking that question.

Re: Show HN: Stop Claude Code from forgetting everything

#210

Post by d4rkp4ttern »

christinetyip wrote: post #185

A lot of the discussion here is about memory inside a single tool, which makes sense. I’m curious how people think about portability: e.g. letting Claude Code retrieve context that was created while using Codex, Manus, or Cursor, or sharing specific parts of that context with other people or agents. At that point, log parsing and summaries become per-tool views of state rather than shared state. Do people think a sha…

The aichat tool I mentioned in another comment [1] enables exactly this type of cross-agent work-continuation, specifically between Claude-Code and Codex-CLI.

[1] https://news.ycombinator.com/item?id=46433213

Post reply on HN