Codex import checklist

Use the built-in Codex import. Then verify the harness gaps.

OpenAI's new Codex switch flow can import an existing agent setup and create an import checklist. That is the right starting point. The next step is validating the parts of a Claude Code setup that are not just files.

Bring Your AI is not a replacement for the Codex onboarding importer. It is a local-first migration and validation tool for users who need explicit notes, merge policies, rollback snapshots, and cross-harness checks before Codex starts editing code.

What the Codex importer should cover first

Global instructionsRules and preferences that can become Codex guidance.

Project instructionsRepo-level operating notes and workflow files.

Skills and pluginsReusable workflows with their local assets.

MCP configurationServers that need wrapper-format translation and secret review.

The validation checklist

1. Hooks are not portable by default.

Claude Code lifecycle hooks and Codex hooks do not have the same shape. A migration should record the intent of each hook and whether Codex can enforce it. If it cannot, the target agent needs a validation note, not a silent copy.

2. Per-agent restrictions need an enforcement check.

A subagent or skill may depend on Claude Code-specific metadata, tool allowlists, or lifecycle behavior. Treat those as behavior contracts. Verify the target can enforce them before trusting the imported setup.

3. MCP env values should not become literal secrets.

MCP configuration often points at API keys, OAuth tokens, or local keychain helpers. The target config should preserve references and redactions. It should not paste secret values into a new TOML or JSON file.

4. Session artifacts are context, not instructions.

Old transcripts, logs, and handoff files are useful for continuity. They can also carry stale goals and project-specific assumptions. Import them only as analytics or review material unless you intentionally want them in the agent's active instruction path.

Where Bring Your AI fits

Bring Your AI runs locally and leaves the source harness unchanged. The basic Claude Code to Codex path is:

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 output includes validation notes for non-equivalent behavior, merge-first writes into the target setup, and rollback snapshots before changes. The remote MCP at bringyour.ai/mcp is no-data; it only helps agents discover the local CLI and supported moves.

For the instruction-file layer specifically, see AGENTS.md vs CLAUDE.md for Codex migration.

Agent-readable commerce

Agents can inspect the product and start a human checkout handoff without parsing the site:

curl -s https://bringyour.ai/api/v1/catalog
curl -s https://bringyour.ai/.well-known/agent.json
curl -s https://bringyour.ai/.well-known/commerce.json

Buy lifetime access Read the full migration guide

Sources: OpenAI Codex switch page; Bring Your AI OpenAPI spec; Bring Your AI agent manifest.

← back to bringyour.ai