Automatic project memory for Claude Code. Also works with Cursor and Codex. Now in Anthropic's Claude plugin directory. - Avinash-jetwani/jevmem
41 comments
I have read through the project and I still don't understand what this thing is for and why it is to be preferred over the harness's native memory management tools.
My previous rule was that I never use AI for writing that expresses my own opinions or tries to be convincing (anything on my blog for example) but I'll let it do technical documentation.
The top of a README is about convincing and explaining why I built something though, which means it should fit my no-AI policy after all.
I don't know why the models were generally trained to be so brief, but it's definitely not the way anyone I know actually writes. A second pass is always a good idea to clean this stuff up. And, thankfully, the models are all pretty good at that.
Well duh. RL can only train behaviors that can be defined. Clarity and elegance are damn subjective.
Also, I doubt we'll ever get AI to understand what clarity is to a human. They have such enormous contexts that what's clear to them is not clear to us.
Maybe give it a try next time you write a readme with agents. That and giving it an example of good README in real world repos can increase dramatically the likelihood of synthesizing a serviceable README.
To me, this seems like a design error. You're polluting context with false/outdated information (even if the LLM is instructed to ignore it). The biggest issue with the memory systems built into Claude et al. is that they're terrible at pruning old/conflicting information as the project evolves, so I'd hope a replacement would do something to improve that.
Everything is inundated with info about other things tried.
Comments and docs flooded with things found out in the process when you want something about the info you need to know now.
- All decisions get logged to DECISIONS.md, sequentially
- Before writing a decision, read through past decisions to see if any conflicts
- If no conflicts, encode the decision into the CODE.md
- If any conflicts, ask a Tribunal of 3 agents to find a resolution—each of them should be prompted in slightly different ways
I've only done this for one pretty big project but so far it seems to be working well
You may want the old decision in the audit trail so you know why something changed without putting that old decision back into the model context every time
I think memory systems need a pretty strict separation between active memory and historical memory
> Next session, the relevant lines are added to Claude's context.
At least that's how I interpret it? If it is adding superseded decisions, that does seem bad.
I suppose if you could guarantee that the nondeterministic model can not only know all of those disparate pieces of information, but connect them together in that order, and arrive at a decision that it was abandoned because it was already visited and tried, every time.
Just start a cheap chinese agent in a context where it has only one tool, and JSON-schema constrain that toolcall to the response shape you want. Prompt the agent to make only one tool call and not speak. Done.
Side note: conspiracy theorists say that jev is a qwen model fine tuned but who know if true
Read the full thread on Hacker News →
Related stories
- Lobsters · 86 points · about 1 year ago
- Hacker News · 1 points · 8 days ago
- Hacker News · 2 points · 7 days ago
- Lobsters · 3 points · 6 months ago
- Hacker News · 4 points · 12 days ago
- Hacker News · 1 points · 11 days ago