Credentials. The .env file holds provider API keys, so keep it local and out of version control, and avoid pasting keys into agent prompts or logs.
Who it is forA developer building a persistent assistant that must remember user preferences across sessions and recall them later.
The problemThe assistant forgets details from earlier conversations, and the team needs memory that keeps original observations with timestamps and provenance.
The outcomeA local memory cache built from your observations, plus an answer to a question about a stored preference, produced by the OpenAI-compatible model.
What you need first
- Python 3.11 or newer and a terminal
- A local copy of the repository (the README assumes you run commands from the repository root)
- For live runs: a TypeSafe API key and an OpenAI API key, plus network access, since live runs may incur charges
- For benchmarks: the LoCoMo dataset placed at data/locomo10.json, obtained from its original distributor per the data setup guide
Steps
- Create a
.envfile in the repository root withTYPESAFE_API_KEY=your-typesafe-keyandOPENAI_API_KEY=your-openai-key. - Format your data as a JSON list of strings or objects with
content, an optional ISO 8601timestamp, and optionalmetadata. - Build the cache with
python -m jev_mem --mode build --input examples/observations.json --jev-config config/jev_mem.json --cache-dir ./jev_mem_cache/app, replacing the input path with your file. (inferred, check the README) - Query it with
python -m jev_mem --mode query --question "What reminder does Mira prefer?" --jev-config config/jev_mem.json --cache-dir ./jev_mem_cache/app, replacing the question with your own. (inferred, check the README)
Prompt for your agent
In the Jev-Mem repository at <target-folder>, build a cache from <input-json-file> using `python -m jev_mem --mode build` with config/jev_mem.json, then query it with `--mode query` using the question <question>. Return the answer and confirm that the cache folder was created locally.
Caveat. Live runs send your text to the configured providers and may incur charges, and the README says to keep keys, conversations, and caches local, so review SECURITY.md before using private data.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page