jevmemjevmem

Does jevmem need a key, what does it cost, and what are its limits?

jevmem needs a TypeSafe API key; deciding what to save costs $0.00018 per message on that key; a local model is not a supported mode; your team gets the memory file through git; and the known limits are listed at the end of this page.

Last updated: · jevmem 0.7.8 · Install · Source on GitHub

The cost is the average over 66 held-out turns with jevmem 0.7.3, one run on 2026-10-15, at TypeSafe's listed price for Jev (results). To set jevmem up: install.

Do I need a key? #

Yes: jevmem needs a TypeSafe API key, because Jev, the model that decides what to save, runs on TypeSafe's API. jevmem key saves it in ~/.jevmem/env, readable only by you. You need no OpenAI or Anthropic key: jevmem writes each line itself unless you set writer in jevmem.config.json.

What does it cost? #

jevmem itself is free and open source (MIT). The requests it makes to Jev are billed by TypeSafe to your key.

Both are input tokens at $0.042 per million, the price in TypeSafe's launch post; check TypeSafe's own pricing for what your key is charged. Every request is logged in .jevmem/log.jsonl, and jevmem stats adds them up. The whole table: docs/cost.md.

Can jevmem run on a local model? #

Not as a supported mode. It was tried once, on 2026-10-02, with a local model server, Ollaya 0.9.0, on an Apple M4 with 16 GB, next to a Jev run of the same set the same afternoon. On the 66 held-out turns, in jevmem's default mode, Jev was right on save or skip for 65/66 turns at a median of 0.23 s a turn; winnow:e4b for 60/66 at 28.5 s; laya:typed-decisions for 19/66.

The results files: Jev, winnow:e4b, laya:typed-decisions. The limits of that test: one run each, on one Mac, with two models; the set was written for Jev's behaviour; and winnow:e4b was measured on these 66 turns only, not on recall or the guard.

Does my team get the memory through git? #

Yes: JEVMEM.md is a file in your repo, so your team gets the same file through git, and a change to it can be reviewed in a pull request like code. Lines a teammate or a pull request adds are checked before Claude sees them: on a 44-line test set (2026-09-25), that check blocked 20 of 22 planted lines, with 0 false blocks on 22 legitimate rules (results). The scores behind each line stay on the machine that saved it, in .jevmem/, which is not in git.

Which tools does it work with? #

Saving is automatic in Claude Code and, since 0.7.4, in Cursor, where Cursor's hooks save each finished agent turn (since 0.7.6 from the jevmem plugin for Cursor, or from the files jevmem init --tool cursor writes); and in Codex while jevmem watch runs. Cursor, Codex and Claude Desktop reach jevmem over MCP, a standard way for an AI tool to call another program, when the agent asks for it; the Cursor plugin's server runs in every window, while a project's own .cursor/mcp.json server starts off until you turn it on once (the step). In Cursor, on 10 held-out chats captured before the code (24 turns), the first run paired 21 of 24 turns whole, the prompt with the whole reply; a reader fix came from that run, and the second run paired 24 of 24, with what to save right in 21 of 24 (measured).

Saving Bringing it back
Claude Code Automatic, every turn Automatic, every prompt
Codex Automatic while jevmem watch runs When the agent asks, over MCP
Cursor Automatic, every finished agent turn (0.7.4; the plugin since 0.7.6) When the agent asks, over MCP (the plugin's server runs in every window; a project's own server needs one toggle in the Cursor app, the step)
Claude Desktop When you ask it to, over MCP When you ask it to, over MCP

The MCP server is on the MCP Registry as io.github.Avinash-jetwani/jevmem. Client setup: docs/mcp.md · docs/install.md.

What leaves my machine? #

Message text is sent to TypeSafe to be scored, with common secrets scrubbed first, and only from a project you have turned on. The whole list: What leaves my machine?

What are jevmem's limits? #

Known limits #

Honest limits #

The limits, in short #

Every limit, with the numbers: the FAQ.