OpenAI Codex

Install coree as a Codex plugin.

coree supports OpenAI Codex via the Codex plugin system.

Install

codex plugin marketplace add coree-ai/codex
codex plugin add coree@coree

The first command registers the marketplace source from GitHub. The second installs the plugin into Codex's plugin cache, which registers the coree MCP server and hooks.

Hooks

The plugin bundles hooks automatically. Codex asks you to review and trust command hooks before they run; use /hooks after installing or updating the plugin.

HookPurpose
SessionStartInjects stale notes and session context at the start of each session and after compaction
UserPromptSubmitInjects relevant memories before each user prompt (up to 8 000 tokens)
StopCurrently returns an empty JSON response while stop-continuation behavior is verified

Without these hooks, coree still works as an MCP server - you can call tools manually. The hooks add automatic context injection equivalent to the Claude Code and Gemini CLI integrations.

What gets installed

The plugin installs to the Codex plugin cache:

The directory contains:

The binary is fetched via npx on first use and cached in ~/.npm/_npx/ (Linux/macOS) or %LocalAppData%\npm-cache\_npx\ (Windows).

Environment variables

If you use coree's remote sync, the following env vars must be set in your shell so Codex forwards them to the MCP process:

The plugin's .mcp.json already lists these in env_vars so Codex will forward them if they are present in your shell environment.

# Linux / macOS (bash/zsh)
export COREE__MEMORY__REMOTE_AUTH_TOKEN=your-token
export COREE__MEMORY__REMOTE_URL=libsql://your-db.turso.io
# Windows (PowerShell)
$env:COREE__MEMORY__REMOTE_AUTH_TOKEN = "your-token"
$env:COREE__MEMORY__REMOTE_URL = "libsql://your-db.turso.io"

Updating

codex plugin add coree@coree

Codex checks the marketplace source for a new version and updates the plugin cache if the version has changed. Use /hooks after updating to review and trust any new hook commands.

Verify

After installation, start a session and run:

call the diagnose mcp tool

Diagnose reports the current server state and any configuration issues.

Troubleshooting

Plugin hooks do not fire: Run /hooks in Codex and verify the coree hooks are trusted. Codex asks you to review command hooks before they run - they will not fire until trusted.

Server starts but times out on first use: First-run downloads the platform binary and embedding model, which can take 30-90 seconds. Wait for the download to complete - subsequent starts are fast.

MCP server does not appear in the tool list: Restart Codex completely. Check that the plugin was installed to the correct cache directory (see paths above).

npx hangs or fails: Ensure Node.js 18+ is installed. Check that your network allows npm registry access (registry.npmjs.org).