me codex¶
Codex CLI integration commands.
Commands¶
- me codex install -- register
meas an MCP server with Codex CLI - me codex import -- import Codex sessions from
~/.codex/sessionsand~/.codex/archived_sessions
me codex install¶
Register me as an MCP server with Codex CLI.
| Option | Description |
|---|---|
--api-key <key> |
API key to embed in the MCP config. |
--server <url> |
Server URL to embed in the MCP config. |
If no --api-key or --server is provided, values are resolved from ~/.config/me/credentials.yaml (set by me login and me engine use).
This is equivalent to me mcp install codex -- see me mcp for the multi-tool installer.
me codex import¶
Import Codex sessions from ~/.codex/sessions/YYYY/MM/DD/rollout-*.jsonl and ~/.codex/archived_sessions/*.jsonl.
See agent session imports for the full option reference, tree layout, idempotency rules, content shape, and metadata schema.
Codex sessions include git commit, branch, and remote URL in session_meta, so the importer captures all three. Both the recent on-disk format (with a leading session_meta line wrapping payloads in response_item / event_msg) and the legacy format (bare response-item-like objects per line) are handled.
Reasoning and function-call response items don't always carry a native id. In those cases the importer synthesizes a stable id from (session_id, type, ordinal) so re-imports remain idempotent.
Injected Codex wrapper messages like # AGENTS.md instructions ..., <user_instructions>...</user_instructions>, <environment_context>...</environment_context>, and <turn_aborted>...</turn_aborted> are ignored.