DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to use one project memory across Cursor and Codex with Jevmem

Point Cursor or Codex at the same JEVMEM.md so the agent reads the same saved lines.

Who it is forA developer who switches between Claude Code, Cursor and Codex on the same project and wants each agent to know the same decisions.

The problemEach tool starts without the decisions made in the others, so the agent in one editor can contradict a choice made in another.

The outcomeCursor saves finished agent turns automatically and Codex saves while watch runs, with both reading the shared JEVMEM.md over MCP when asked.

What you need first

  • A TypeSafe API key from https://console.typesafe.ai/keys, which jevmem's requests are billed to
  • Claude Code 2.1.273 or later
  • npm, to install the jevmem CLI that the plugin runs
  • A project folder in a git repo, so JEVMEM.md can be committed and shared

Steps

  1. Run npm install -g jevmem if the CLI is not installed yet.
  2. In the project folder, run jevmem init --tool cursor for Cursor or jevmem init --tool codex for Codex. (inferred, check the README)
  3. For Codex, run jevmem watch in the project folder while you work.
  4. In Cursor, install the Jevmem plugin from the Cursor Marketplace once it is listed there, then run jevmem setup in each project.

Prompt for your agent

In the repo at <project-folder>, run `jevmem init --tool codex` and then confirm that jevmem watch starts without errors. Expected output: a running watch process and no setup errors. Verify that a decision made in a Codex chat appears as a line in JEVMEM.md.

Caveat. In Cursor and Codex the agent must ask for Jevmem over MCP to read memory, and a project's own Cursor MCP server starts off until it is turned on once in the Cursor app.

Share: 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