Codex Memory Curator

Goal

Audit Codex memory as user-owned durable state; classify stale, unsafe, duplicated, or misplaced claims and route review, planning, persistence, and cleanup. Even when invoked from Cursor, inspect only Codex memory/config, not Cursor state.

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

• Use for review, placement, configuration, planning, or cleanup of Codex memory and its durable configuration.
• Use when memory is stale, conflicting, sensitive, noisy, cross-repository, or causing degraded behavior.

When not to use

• Do not use for ordinary docs, generic prompt work, or Cursor state unless Codex memory/config is explicitly involved.
• Keep review requests read-only and inspect no personal files beyond Codex memory/config plus the minimum repository evidence needed for conflicts.