rememlisted

# Remem Remem gives Codex durable project memory through the `remem` MCP server. Use it when the answer depends on prior sessions, project preferences, saved decisions, workstreams, or memory health. ## Retrieval - Search remem before answering questions about prior project context, remembered preferences, older bug fixes, workstreams, or "what did we decide before". - Use compact `search` results first, then call `get_observations` for selected IDs when exact content is needed. - Use `search_raw` only when curated search misses an exact phrase or chat transcript detail. - Treat memory as evidence, not current truth. Verify live repo, GitHub, filesystem, and command output when the fact can drift. ## Saving Memory Save a durable memory after: - architecture decisions, including what was chosen and what was rejected - bug fixes with a verified root cause, fix, and prevention - important project discoveries with future implications - explicit user preferences that should affect future sessions Use the active repo/workspace `project` plus a stable `topic_key` so repeated saves update the same memory instead of creating duplicates. For project memories, pass `project` as the active repo/workspace path and pass `branch` when it is known. Use `scope: "global"` only for explicit cross-project user preferences. ## Activation The plugin exposes MCP tools as soon as Codex loads `.mcp.json` and the runtime manager can resolve a matching `remem` binary. Automatic context injecti