Command reference ยท Codex CLI
/memories
Sets whether the chat may use or create memories, when Memories is available.
Determines whether the current chat may access memories (recollections across sessions) or generate new ones. The terminal CLI docs describe this literally as toggling "memory injection or memory generation", without leaving the terminal interface (TUI).
The feature depends on an availability condition: "if memories is available". According to Codex release notes (rust-v0.145.0 from 07/21/2026 โ just a few days before this was written), the internal feature flag for memories was only recently stabilized there, alongside a paginated session history still marked as experimental. So the feature set is still being expanded, and older Codex versions may not know the command yet, or only in a limited form. According to the source code, /memories also can't be called while Codex is actively working on a task โ you have to let the current turn finish before the command responds.
โ WHEN TO USE IT?
Turn off memories for a sensitive chat
Call /memories and disable creating new memories for this one chat before discussing confidential details.
Quickly check whether memories is active
Open /memories to check whether the current chat is currently using or generating memories, without leaving it for settings.
โ WHEN NOT TO?
Memories not available in the installed version
According to release notes, the feature flag was only stabilized on 07/21/2026; older or restricted installations still lack the command.
Better: update Codex CLI or keep working without memories
While Codex is still working on a task
According to the source code, /memories is one of the commands locked while a task is running.
Better: wait for the running task to finish, then call /memories
SOURCES
- Codex CLI docs: Slash Commands โ learn.chatgpt.com
MORE COMMANDS ยท Codex CLI