Thread

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

62 points · 49 comments · avinashjetwani

anthuswilliams · 1790353553 · focus · HN ↗
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.
1. avinashjetwani · 1790362064 · focus · HN ↗
  Fair. Short version: Claude Code (and friends) already keep session/auto memory, but it lives in the harness. jevmem’s job is a JEVMEM.md in the repo so decisions travel with the project across sessions and tools. After each turn, Jev scores whether anything is worth keeping (decision, constraint, bug, change of mind). Capture is fully automatic in Claude Code today; Cursor/Codex need the agent/MCP path (or jevmem watch for Codex). If the README buried the "why", that’s on me.

Unofficial Hacker News client; not affiliated with Y Combinator.