Migration tools

Use Codex import first. Validate the harness locally.

The migration tool choice depends on what has to move: one instruction file, or a full harness with hooks, MCP servers, skills, memories, and rollback requirements.

The remote Bring Your AI surfaces stay no-data. They help agents discover the product, quote the license, and find the local command path; they do not accept harness files or config contents.

Tool comparison

Codex importBest first step for account-side migration and an initial checklist.
Manual AGENTS.md editsWorks for small repos where the only real state is one instruction file.
Bring Your AI CLILocal preview and merge-first migration for real harness state.
Remote MCP discoveryNo-data target discovery, install instructions, quote, and checkout handoff.

Decision rules

  1. If the only state is one instruction file, the first-party import plus a manual diff may be enough.
  2. If the setup includes hooks, MCP servers, skills, managed policy, or generated memories, run a local validation pass.
  3. If MCP config includes env, Keychain, 1Password, or vault helpers, preserve references instead of copying values.
  4. If session logs are useful history, keep them as notes instead of active instructions.
  5. If Codex will write production code after import, create rollback proof first.

Local validation path

curl -fsSL https://bringyour.ai/install.sh | sh
bringyour preview --from claude-code --to codex
bringyour migrate --from claude-code --to codex --policy merge

The agent-readable version of this comparison is available at /claude-code-to-codex-tools.json.

Buy lifetime access Read the audit
back to bringyour.ai