# AI use cases for Codex Memories (libenxier-beep/codex-memories)

Repo: [libenxier-beep/codex-memories](https://github.com/libenxier-beep/codex-memories) | Use cases: 3 | Page: https://dedupedai.com/use-cases/libenxier-beep-codex-memories/

Codex Memories is a local-first persistent memory runtime that lets OpenAI Codex recall project decisions across sessions from a Git-backed store.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Give Codex a local memory of project decisions: https://dedupedai.com/use-cases/libenxier-beep-codex-memories/install-local-codex-memory/
- Check the memory loop with a throwaway demo first: https://dedupedai.com/use-cases/libenxier-beep-codex-memories/try-memory-demo-before-install/
- Roll back progressive recall without losing memory: https://dedupedai.com/use-cases/libenxier-beep-codex-memories/rollback-progressive-recall/

## How to give Codex a local memory of project decisions with Codex Memories

Repo: [libenxier-beep/codex-memories](https://github.com/libenxier-beep/codex-memories) | Difficulty: Intermediate | Time: 30 min | Basis: From the README

Install a local, Git-backed memory so Codex can recall decisions across sessions.

**Who it is for:** A developer using Codex on a long-running project who keeps repeating the same decisions and constraints in new sessions.

**The problem:** Codex starts each session without the project decisions made in earlier sessions, and a hosted memory service would send private notes off the machine.

**The outcome:** A runtime, a private Git-backed authority, and a local sidecar are installed, and doctor reports the deployment state, including whether hook integration still needs review.

### Steps

1. `git clone https://github.com/libenxier-beep/codex-memories.git`
2. `cd codex-memories`
3. `./install.sh`
4. `~/.local/share/codex-memories/bin/codex-memories doctor`
5. Open the generated hooks.merge-plan.json under ~/.local/share/codex-memories and merge it into your hooks configuration yourself, then run the doctor command again.
6. `~/.local/share/codex-memories/bin/codex-memories recall "governed local memory"`

### Prompt to paste into your agent

```text
Clone the codex-memories repo from https://github.com/libenxier-beep/codex-memories, run ./install.sh, then run ~/.local/share/codex-memories/bin/codex-memories doctor. Report the integration line; it should show review_required until the hook plan is merged, and confirm the Authority path is ~/.codex/memories.
```

### Caveat

Automatic capture and recall stay inactive until you merge the generated hook plan, and Windows is not yet validated.

Risk, credentials: Recalled memory can enter Codex model context, so keep secrets and client data out of the memory authority and review what your host's data settings send to the model.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/libenxier-beep-codex-memories/install-local-codex-memory/

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

Repo: [libenxier-beep/codex-memories](https://github.com/libenxier-beep/codex-memories) | Difficulty: Intermediate | Time: 15 min | Basis: From the README

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

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

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

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

### 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 to paste into your agent

```text
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.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/libenxier-beep-codex-memories/try-memory-demo-before-install/

## How to roll back progressive recall without losing memory with Codex Memories

Repo: [libenxier-beep/codex-memories](https://github.com/libenxier-beep/codex-memories) | Difficulty: Advanced | Time: 30 min | Basis: From the README

Switch from progressive retrieval back to legacy recall while keeping stored memory.

**Who it is for:** A developer testing the progressive retrieval runtime who sees worse recall results and wants the previous behavior back quickly.

**The problem:** Experimental retrieval can misbehave in a real project, and switching it off should not require deleting memory data.

**The outcome:** Progressive recall is disabled through the rollback command, and memory data remains in place for the legacy path.

### Steps

1. `git clone https://github.com/libenxier-beep/codex-memories.git`
2. `cd codex-memories`
3. `python3 scripts/agent_memory.py --help`
4. `python3 scripts/agent_memory.py --progressive-state-dir /absolute/owner-only/state progressive enable` (inferred, check the README)
5. `python3 scripts/agent_memory.py --progressive-state-dir /absolute/owner-only/state progressive rollback` (inferred, check the README)

### Prompt to paste into your agent

```text
In the codex-memories repo, run python3 scripts/agent_memory.py --progressive-state-dir <owner-only-state-dir> progressive rollback. Report the command output and confirm the memory authority under ~/.codex/memories still exists and was not deleted.
```

### Caveat

The README reports that a compact hidden seal scored 3 of 6 on Recall@5 and was rejected, so progressive retrieval is not yet shown to beat simpler recall in general.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/libenxier-beep-codex-memories/rollback-progressive-recall/