Jevmem – automatic project memory for Claude Code, built on Jev

avinashjetwani

jevmem watches Claude Code, Cursor & Codex chats and keeps a JEVMEM.md in your repo up to date. After each message, Jev (TypeSafe) decides whether anything is worth remembering — a decision, a bug, a change of mind — and writes the keepers to that file. Reversed decisions get marked superseded. Install: npm i -g jevmem (needs a TypeSafe API key) Held-out check on 66 messages (23 Sep 2026) vs six frontier LLMs: save/skip 98.5% (tied with Astra); save+correct kind 95.5% (Astra 98.5%, Opus 97.0%); changes of mind 5/5; median 0.30s via Jev API (~0.6s end-to-end) vs 2.8–4.3s for the LLMs; cost $0.000127/decision. Single run by me — treat 1–2 message swings as noise. Limits: early v0.4; fully automatic only in Claude Code today (Cursor/Codex via agent/MCP); messages go to the TypeSafe API with secrets stripped; if the API is down it skips.

shaohua

something I always wanted

anthuswilliams

One interesting quirk of the AI-written READMEs these days is how they can include every detail on how it works, thoroughly document every optional flag, known limitation, experimental result, and still not communicate the essence of the project and the problem it solves. 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.

alpineman

a supercollision of 2024 hype with 2026 hype

saagarjha

Wake me up from this nightmare

rhgraysonii

Curious how this compares to my own tool, https://deciduous.dev I will have to give it a run-through today. I haven't used Jev yet so this should be interesting. I'd be interested to see if any Deciduous users have opinions, too.

rafram

> When you change your mind, the old line is marked superseded, not deleted 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.

joshumax

I’m looking at the LLM-generated SECURITY.md and this thing seems to pump a LOT of information back to some place called TypeSafe AI. That and the AI-generated comments from OP here make a few red flags go up for me.

abraxas

Does it thrash the session's KV cache?

useruser125524

I'd rather make a decision on where else to put the contents of a generated memory file than to maintain a memory layer

octoberfranklin

I really don't undertstand the jev-hype. 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.