xmemo-codex

name	xmemo-codex
description	Use XMemo from Codex to recall project context, capture engineering decisions, preserve handoff state, and configure the hosted XMemo MCP endpoint safely.

XMemo for Codex

Use this skill when a Codex task should use XMemo memory, restore project context, save durable decisions, record working state, or prepare a clean handoff.

Core Positioning

Codex executes development. XMemo lets Codex remember the project.

XMemo is a user-owned, identity-aware memory layer for multi-agent workflows. It helps users carry useful project context, decisions, preferences, and progress across ChatGPT, Codex, Claude, Cursor, Copilot, Gemini, IDEs, CLIs, and other agents.

Codex Connection

The hosted MCP endpoint is:

https://xmemo.dev/mcp

Codex should authenticate through an environment variable instead of writing a bearer token into project files:

[mcp_servers.XMemo]
url = "https://xmemo.dev/mcp"
bearer_token_env_var = "XMEMO_KEY"
http_headers = { "X-Memory-OS-Agent-ID" = "codex" }
env_http_headers = { "X-Memory-OS-Agent-Instance-ID" = "XMEMO_AGENT_INSTANCE_ID" }

Prefer the XMemo CLI setup helper when available:

npm install --global @xmemo/client
xmemo login
xmemo mcp add codex --write
xmemo smoke --client codex

For a one-off invocation without a global install, use npx --yes --package @xmemo/client xmemo <command>.

Memory Workflow

At task start:

1. Recall focused context from XMemo for the current repo, subsystem, and task.
2. Restore a restart snapshot if the task is continuing previous work.
3. Fall back to local repository evidence if XMemo is unavailable.

During architecture or integration work:

1. Capture pending decisions before committing to major tradeoffs.
2. Resolve decisions after implementation or explicit confirmation.
3. Save only durable conclusions, not noisy intermediate reasoning.

At handoff:

1. Update working state with what changed, what was verified, and what remains.
2. Create memory TODOs for concrete follow-up actions.
3. Create a restart snapshot when work is incomplete.

Safety Rules

• Never commit XMEMO_KEY, OAuth codes, cookies, session tokens, or reviewer credentials.
• Treat X-Memory-OS-Agent-ID and XMEMO_AGENT_INSTANCE_ID as non-secret attribution metadata, not authentication.
• Keep recall scoped to the user's request.
• Do not claim Codex official plugin approval until an official review has accepted this package.
• Use synthetic memory data for review demos and screenshots.