Codex

Codex should use a scoped key bound to the Codex source app. The integration supports recall, writeback, Courtroom read, canary/status checks, and pre-turn agent context.

Registry contract

This section is generated from integrations/agent_integrations.registry.json. Edit the registry or generator, not this block.

Field	Value
Integration ID	codex
Label	Codex CLI
Tier	remote_mcp_client
Setup mode	http_mcp
Agent ID	codex
App ID	codex
Source app / actor	source_app=codex, agent_id=codex; key metadata wins over request body hints
Default scope	own
Config paths	~/.codex/config.toml, .codex/config.toml, AGENTS.md
Capabilities	memory.read, memory.write, memory.recall, memory.delete, agent.context, agent.writeback, mesh.read, evidence.read, courtroom.read, canary.read
Supported tools	codexBootstrap, codexCapture, codexStatus, um_store, um_search, um_profile, um_courtroom

Capture policy

MCP bootstrap/capture around coding tasks; reusable workflows go to task, commands/fixes to tool, active scratchpad to working.

Install command(s)

export {{KEY_ENV}}="{{KEY_REF}}"
codex mcp add unified-memory --url {{MCP_URL}} --bearer-token-env-var {{KEY_ENV}}

Verify command(s)

codex mcp list
codex mcp get unified-memory

Environment

{
  "UNIFIED_MEMORY_API_KEY": "{{KEY_ENV_REF}}",
  "UNIFIED_MEMORY_CONTAINER": "{{CONTAINER_TAG}}",
  "UNIFIED_MEMORY_URL": "{{EDGE_BASE_URL}}"
}

Risk notes

• Prefer bearer_token_env_var over literal key values.
• Keep AGENTS.md as the repo-local operating guide.

Official upstream docs

https://developers.openai.com/codex/config-reference

Scope and capabilities

Setting	Value
Source app	codex
Default container	jeethendra
Default scope	own
MCP URL	https://edge-api.jithendranara.dev/mcp
Key env var	UNIFIED_MEMORY_API_KEY

Install

export UNIFIED_MEMORY_API_KEY="<scoped-key>"
codex mcp add unified-memory \
  --url https://edge-api.jithendranara.dev/mcp \
  --bearer-token-env-var UNIFIED_MEMORY_API_KEY

Keep the key in your user environment or secret store, not in repo files.

Verify

Run a tool discovery or canary from Codex. A healthy check should show memory tools and confirm the effective source app is codex.

codex mcp list

Runtime behavior

• Pre-turn context reads Codex working/session memory plus approved canonical owner facts.
• Post-turn writeback stores evidence privately first.
• Promotion to shared memory requires trust/review gates.
• Courtroom is available for important memories and conflicts.

Common mistakes

• Do not paste an admin key into Codex config.
• Do not rely on body agent_id overrides; key metadata wins.
• Do not write back full reasoning transcripts or assistant dumps.