Jevmem surfaced on Hacker News with 49 points and 36 comments as an automatic memory layer for Claude Code projects.
It is built directly on the Jev framework to store and retrieve project context without manual prompting.
What It Is and How It Works
Jevmem runs as a background process that watches Claude Code sessions. It extracts key decisions, file references, and task states, then writes them into a persistent Jev store.
On the next session start, the stored entries are injected automatically so Claude resumes with prior context intact.
The tool requires no changes to Claude Code itself and works through the existing Jev API.
Key Specs from the Repository
Tool: Jevmem | Base: Jev framework | Target: Claude Code | Source: GitHub (Avinash-jetwani/jevmem) | Discussion: 49 points, 36 comments on Hacker News
No parameter counts or VRAM figures are listed because Jevmem is a lightweight wrapper rather than a model.
How to Try It
Clone the repository and follow the README setup.
Install the Jev dependency first, then run the jevmem watcher in the project directory.
Point Claude Code at the same folder so the memory store is discovered on launch.
Pros and Cons
- Automatic context capture removes repeated setup prompts.
- Works offline once Jev is installed.
- Limited to projects already using Claude Code.
- No built-in search or editing UI for stored memories.
- Relies on Jev stability; any Jev breakage affects Jevmem.
Alternatives and Comparisons
| Feature | Jevmem + Jev | Manual Claude Projects | Custom RAG scripts |
|---|---|---|---|
| Automatic capture | Yes | No | Partial |
| Persistent across sessions | Yes | Limited | Yes |
| Setup effort | One-time install | None | High |
| Searchable memory | No | Basic | Yes |
Who Should Use This
Developers running repeated Claude Code sessions on the same codebase gain the most. Teams that already maintain Jev stores can add Jevmem with minimal overhead.
Skip it if you prefer full control over context or already use a dedicated vector database for project history.
Bottom Line
Jevmem fills the gap between Claude Code’s stateless sessions and the need for continuous project memory by leveraging the existing Jev layer.
Early HN comments focus on whether the automatic extraction is reliable enough for production codebases. The repository remains the primary place to test current behavior.
Top comments (0)