Mem0 persistent memory integration for Codex. Automatically retrieve relevant memories at the start of each task, store key learnings when tasks complete, and capture session state before context is lost. Use the mem0 MCP tools (add_memory, search_memories, get_memories, etc.) for all memory operations.
You have access to persistent memory via the mem0 MCP tools. Follow this protocol to maintain context across sessions.
search_memories with a query related to the current task or project to load relevant context.get_memories to browse all stored memories for this user.Extract key learnings and store them using the add_memory tool:
{"type": "decision"}{"type": "task_learning"}{"type": "anti_pattern"}{"type": "user_preference"}{"type": "environmental"}{"type": "convention"}Memories can be as detailed as needed -- include full context, reasoning, code snippets, file paths, and examples. Longer, searchable memories are more valuable than vague one-liners.
If context is about to be compacted or the session is ending, store a comprehensive session summary:
## Session Summary
### User's Goal
[What the user originally asked for]
### What Was Accomplished
[Numbered list of tasks completed]
### Key Decisions Made
[Architectural choices, trade-offs discussed]
### Files Created or Modified
[Important file paths with what changed]
### Current State
[What is in progress, pending items, next steps]
Include metadata: {"type": "session_state"}