migrate-agents-to-codex

Migrate Claude agent definitions to Codex format by converting YAML frontmatter and markdown bodies into native Codex custom-agent TOML or backward-compatible markdown files, applying field mapping and MCP namespace normalization automatically.

MCP namespace normalization standardizes MCP server references in Claude agent definitions so they validate correctly against project-level .codex/config.toml MCP server definitions during the Codex migration process.

Tier-based classification routes Claude agents through Mechanical, Assisted, or Hand-Authored migration paths based on complexity signals like hooks, MCP tool count, and body length to determine the required conversion effort.

Yes, the Codex migration process validates migrated agent definitions against project-level .codex/config.toml MCP server definitions to ensure runtime hints, skill dependencies, and delegation behavior are preserved correctly.

Yes, migrating agents to Codex preserves runtime hints, skill dependencies, and delegation behavior by mapping YAML frontmatter fields directly into the native Codex TOML structure during conversion.

Automated Claude to Codex agent migration may require manual intervention for Hand-Authored tier agents with high complexity, using an adversarial compliance audit and auto-fix loop to converge on native Codex artifact quality.