What problem does it solve? Moving an existing Claude Code setup to Codex requires manually rewriting instruction files, slash commands, subagents, hooks, and MCP server configuration into Codex formats like AGENTS.md, .agents/skills, .codex/agents TOML, and .codex/config.toml, which is error-prone and tedious. ## Core Features & Use Cases - Automated surface conversion: Converts CLAUDE.md instructions, .claude/commands, .claude/skills, .claude/agents, settings hooks, and .mcp.json MCP servers into their Codex equivalents with partial-mapping caveats preserved as manual-review notes. - Plan, doctor, and validate workflow: Supports --scan-only, --plan, --doctor, --dry-run, and --validate-target modes so you can inspect readiness, staged artifacts, and post-migration validity before and after writing files. - Use Case: You have a project with .claude/commands, three subagents, and an .mcp.json file. Run the migrator against ./.claude/ targeting ./.codex/, review the generated report table, fix flagged manual items, and validate the resulting Codex configuration. ## Quick Start Migrate my Claude Code configuration from ./.claude/ into Codex files under ./.codex/ and show me the migration report.