codex - 💡(How to fix) Fix Scoped memory management for Codex (global, project, hybrid, and per-thread options) [2 comments, 2 participants]

What variant of Codex are you using?

CLI and IDE Extension

What feature would you like to see?

I would like Codex memories to support explicit scope management instead of relying only on a global memory store.

Today, memory appears to be effectively global under the current CODEX_HOME, which can cause cross-project contamination over time. In practice, many memories are highly specific to one repository, one codebase, or one workflow, and should not automatically influence unrelated projects.

I would like Codex to support configurable memory scopes such as:

• Global: shared across all projects
• Project: isolated to the current project/repo/worktree
• Hybrid: use both global and project memory, with project memory taking priority
• Thread-only / no carryover: keep memory local to a thread/session and do not reuse it elsewhere

It would also be useful to have basic memory management controls, for example:

• view whether a memory is global or project-scoped
• promote or move a memory between scopes
• clear memory only for the current project
• optionally disable project memory inheritance from global memory

This would make Codex much more reliable for users who work across multiple repositories with different standards, conventions, and domain-specific context.

Additional information

This becomes more important as memory grows over time. A pattern, preference, or instruction that is useful in one project may be undesirable or even harmful in another. The current behavior can also save very specific project details in a shared memory pool, which makes reuse less precise and increases the chance of irrelevant memory retrieval.

A good solution could be:

• a configurable memory policy in settings/config
• automatic project namespacing based on repo root or worktree
• optional hybrid retrieval with clear precedence rules
• commands or UI to inspect and manage memory by scope

This would improve long-term memory quality, reduce context bleed between projects, and make memory safer and more predictable for multi-project workflows.