DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to check the memory loop with a throwaway demo first with Codex Memories

Run a synthetic commit, index, and recall cycle before installing anything.

Short answer: git clone https://github.com/libenxier-beep/codex-memories.git; then cd codex-memories; python3 scripts/codex_memories.py demo. All steps.

Who it is forA developer who wants to see how a local Codex memory behaves before giving it access to real project notes.

The problemInstalling a memory runtime into a working Codex setup is hard to justify without seeing a commit, index, and recall cycle work first.

The outcomeThe demo reports PASS and shows a made-up project decision recalled in a new process, and your existing Codex settings and memories stay untouched.

What you need first

  • Python 3.9+ and Git installed
  • A local Codex installation for the full install (the demo needs no Codex account or API key)
  • Review access to your Codex hooks configuration, since the installer does not edit hooks.json

Steps

  1. git clone https://github.com/libenxier-beep/codex-memories.git
  2. cd codex-memories
  3. python3 scripts/codex_memories.py demo
  4. Confirm the output lists four OK lines and ends with the recalled synthetic Aurora decision.

Prompt for your agent

Clone the codex-memories repo from https://github.com/libenxier-beep/codex-memories and run python3 scripts/codex_memories.py demo. Report whether it prints 'Codex Memories demo: PASS' and quote the recalled line; verify that no files under ~/.codex/memories were created.

Caveat. The demo uses only a synthetic project decision and does not show retrieval quality on real project notes.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for libenxier-beep/codex-memories and "Check the memory loop with a throwaway demo first"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer