Codex
Codex can remember you and your projects: your preferences, your team's decisions and the conventions of each project, kept across sessions and machines. The Geniffy plugin does it by itself. The MCP server on its own gives Codex the memory tools, for when you ask. The CLI and the IDE extension share the same configuration.
The plugin
Install it
codex plugin marketplace add Geniffy/geniffy-codexIn Codex, open /plugins, choose Geniffy and install it. Codex asks you to sign in to Geniffy for the
memory tools: sign in and press Allow.
Turn on automatic memory
Type geniffy login in Codex, once. Your browser opens Geniffy: press Allow, and there is no key to copy.
The first time, Codex asks you to review the plugin's hooks: open /hooks and trust them. The hooks run with
Node.js 18 or later.
From then on, each session starts with what Geniffy remembers about you and the project, and each turn is saved
in the background when Codex finishes it, with secrets and code blocks left out. Searching your memory runs
without a prompt; saving, correcting and forgetting ask first. Type geniffy status, geniffy pause,
geniffy resume or geniffy logout in Codex: the plugin answers them itself, and they never reach the model.
It is open source: Geniffy/geniffy-codex.
Only the memory tools
To give Codex the memory tools without the automatic recall and saving, add the MCP server on its own.
Add the server
codex mcp add geniffy --url https://api.geniffy.com/mcpSign in
codex mcp login geniffyYour browser opens Geniffy: sign in and press Allow. Codex connects from your computer, so the approval screen names it as an app on this computer.
In config.toml
The command writes this to ~/.codex/config.toml; you can also write it yourself:
[mcp_servers.geniffy]
url = "https://api.geniffy.com/mcp"With an API key
Where signing in is not an option, have Codex send a Geniffy API key from an environment variable:
[mcp_servers.geniffy]
url = "https://api.geniffy.com/mcp"
bearer_token_env_var = "GENIFFY_API_KEY"