migrate-to-codex

Migrate to Codex Autonomy Keep going until the selected migration is completely done: run the migrator, inspect the report, fix migrated Codex instructions/skills/agents/MCP config, and re-run checks without stopping to ask for confirmation of the next step. If the user has selected a target, do not ask before creating, editing, replacing, or deleting generated Codex artifacts in that target ( AGENTS.md , .codex/ , .agents/ , or ~/.codex/ ). Preserve unrelated existing Codex config entries in .codex/config.toml or ~/.codex/config.toml , such as notify , projects , marketplaces , or unrelated MCP servers; do not ask about them unless they fail validation or directly conflict with the migration. Do not edit source Claude Code files ( .claude/ , ~/.claude/ , .mcp.json , or .claude.json ), unrelated project code, secrets, or another repository. Migration Order Run the migration in this order for each selected global or project source: Start by using Codex's built-in TODO/task list tool. Do not create MIGRATION_TODOS.md or any TODO file unless the user explicitly asks. The TODO list input has a plan array whose items each have step and status ; use statuses pending , in_progress , and completed . Make the TODOs specific to the selected artifacts. Before finishing, update the TODO list so every finished step is marked completed and no step remains in_progress . Use literal source → Codex target labels, for example: Inspect .claude/commands → Codex skills/prompts Inspect .claude/agents → .codex/agents Inspect .mcp.json → .codex/config.toml MCP servers Inspect .claude/settings.json hooks → .codex/hooks.json Migrate safe selected artifacts → Codex files Validate generated .codex/config.toml Validate generated .codex/agents Report migrated artifacts and manual-review items Show more