Codex CLI Turns On Memory v2 by Default and Imports Memories From Other Agents
CodexCodex CLI 0.165.0 turned on memory v2 by default for fresh profiles, so new users get cross-session memory without opting in. The release also lets Codex import memories from external agents into memory v2, which means preferences and context built up in other coding agents do not have to be rebuilt from scratch. Together the two changes make persistent memory a standard part of a new Codex setup.
Key Takeaways
- Memory v2 is now on by default for fresh Codex CLI profiles, so new users get cross-session memory without enabling anything.
- Codex can now import memories from external agents into memory v2, which removes the cold-start problem when switching from other coding tools.
- The default applies only to fresh profiles, so existing profiles keep their current memory settings and nothing changes unexpectedly for current users.
- Persistent memory means preferences, conventions and project context can carry over between sessions instead of being re-explained each time.
- The release also turned on mid-conversation reasoning effort changes by default for supported models, giving developers finer control during a session.
- The same version added GPT-6.1 Terra to the model catalogs and a built-in Google Cloud Vertex AI provider, rounding out a broader 0.165.0 update.
Memory v2 Becomes the Default
Codex CLI 0.165.0, released on October 27, 2026, enabled memory v2 by default for fresh profiles. Until now, anyone who wanted Codex to remember context between sessions had to find and switch on the memory feature. With this release, a newly created profile starts with memory v2 already active, so Codex can carry preferences, project conventions and lessons from earlier work into later sessions without any setup.
The change applies to fresh profiles. Existing profiles keep the settings they already have, so current users will not see their behavior change unexpectedly. Developers who prefer to work without persistent memory can still adjust the setting in their configuration.
Importing Memories From Other Agents
The second half of the change is an import path. Codex CLI 0.165.0 can bring memories from external agents into memory v2. A developer who has already taught another coding agent how they like to work, such as preferred libraries, code style or project background, can move that knowledge into Codex rather than starting with an empty memory store.
This lowers the cost of switching to or trying Codex. It also fits the common situation where a developer uses several agents side by side and wants them to share the same understanding of their projects.
Why It Matters
Persistent memory is most useful when it is already working by the time a developer needs it. Making memory v2 the default for new profiles removes a setup step, and the import option removes the cold-start problem for people arriving from other tools. The same release also made mid-conversation reasoning effort changes the default for supported models, but memory is the change that most affects how a new Codex setup behaves from the first session.