Install proof

Smoke the import before Codex writes code.

A Claude Code to Codex migration is only useful after the target harness is proven locally: instructions, hooks, MCP references, generated artifacts, rollback proof, and the repo's own tests.

This checklist is local-only. The remote Bring Your AI surface does not accept harness files, user rules, API keys, repo paths, MCP config, or file contents.

Command path

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

Proof checks

Diff migrated AGENTS.md and target files against the source intent.
Verify hooks were installed as hooks, not copied only as prose.
Keep MCP secrets as env, Keychain, 1Password, or vault references.
Keep generated transcripts and handoff logs as evidence unless explicitly promoted.
Run the repo's normal validation command before the first Codex write.

Failure modes

Hook driftThe rule text moved but the target enforcement did not.

Secret driftA literal token replaced a secret-manager reference.

Scope driftNested Claude rules collapsed into one root instruction file.

History driftSession logs became active behavior instead of review material.

The agent-readable version is available at /codex-import-smoke.json. Paid-license behavior is documented at /license-verification.

Buy lifetime access Read the checklist

back to bringyour.ai