Codex Memory Curator

Goal

Audit Codex memories as user-owned durable state: expose stale, unsafe, duplicated, or misplaced entries; propose better destinations; add a structured cleanup plan when approval needs precision; and apply cleanup only after a report, backup, and explicit user approval.

When installed or invoked from Cursor, keep the subject scoped to Codex memory files and Codex memory configuration. Do not treat this as a Cursor memory, Cursor rules, or Cursor workspace-state curator.

Core principle

Memory is context, not truth. The latest user request, current repo files, AGENTS.md, package files, ADRs, and live evidence override stored memories.

When to use

• The user asks to review, audit, clean up, prune, rewrite, or remove Codex memories.
• The user mentions ~/.codex/memories, stale memories, memory pollution, or memories making Codex worse.
• The user wants to decide whether an entry belongs in memory, AGENTS.md, repo docs, a skill, config, or deletion.
• The user wants to disable, tune, or audit Codex memory behavior.