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

How to share one project memory across coding agents with Ownmem

Install OwnMem in a repo so Claude Code, Codex, Cursor, and Gemini CLI read the same memory.

  • Top pick
  • Software and DevOps
  • Intermediate
  • 30 minutes
  • From the README
  • Claude Code
  • Codex
  • Cursor
  • Gemini CLI

Who it is forA developer or team lead whose repository is edited by several AI coding agents and who wants every agent to see the same project lessons.

The problemEach agent starts each session without the lessons the team learned the hard way, so the same mistakes get repeated across tools.

The outcomeThe repository holds a .ownmem/ directory of Markdown memories, and each named host gets a recall hook or instructions that read from it.

What you need first

  • Node.js 20.6 or newer
  • A Git repository that should own the project memory
  • At least one supported AI coding agent: Claude Code, Codex, Cursor, Gemini CLI, or Grok CLI

Steps

  1. Run npm install --save-dev ownmem inside the repository.
  2. Run npx ownmem init --hook --hosts claude,codex and read the one-time steps it prints.
  3. Reopen each agent, and complete the trust steps that Codex or Grok need if you use them.
  4. Commit the new .ownmem/ directory and the host adapter files with the code.

Prompt for your agent

In the repository grpcer/ownmem, install OwnMem into <target-repo> with the commands in its Quick start, using --hosts for the agents the team uses. Expected output: a .ownmem/ directory and host adapters created, with any one-time host steps listed. Verify that `npx ownmem recall -- "<a known project topic>"` returns a result or an abstention.

Caveat. Codex hooks need three one-time trust steps that OwnMem prints, and Cursor and Gemini CLI need a manual step to register the MCP server.

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