Claude Code to Codex

Keep your agent setup portable before limits interrupt the work.

Claude Code is useful. It is also a hosted product with limits, plan rules, and outages outside your control. The practical move is not to complain harder; it is to keep your harness portable enough that Codex can pick up the work.

Bring Your AI does not send your Claude Code files, Codex files, generated memories, rules, API keys, or session data to Bring Your AI. The remote MCP is no-data. The paid CLI and local MCP run on your machine.

Why this matters now

Recent reporting and user threads show the same pattern: Claude Code users can run into tighter limits, confusing plan access, or service disruption at the exact moment they are depending on the tool for a coding session.

This page does not argue that Claude is bad. It argues that your operating context should not be trapped in one harness.

The local move

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

Preview is free. It tells you whether the move is supported and confirms that original files will not be changed.
Merge is the default posture. Existing Codex setup can be kept unless you explicitly choose a different policy.
Source files are read-only. Claude Code remains intact.
Output includes validation notes. Anything that is not portable 1:1 is written into the target output for review.

What moves cleanly

Global rules and operating preferences.
Skills with a SKILL.md and local assets.
Memory/rule files that can be represented as target-agent guidance.
MCP server configuration, with wrapper-format changes.

What does not move 1:1

Claude Code lifecycle hooks. Codex does not expose the same hook system.
Per-agent restrictions that rely on Claude Code-specific metadata.
Session files, unless you opt in with --include-sessions. When included, they are treated as analytics and continuity artifacts, not instructions.

Agent access

Claude Code can install the local MCP server after the CLI is installed:

claude mcp add bringyour -- /usr/local/bin/bringyour mcp

Codex can use the same local binary as an MCP server:

[mcp_servers."bringyour"]
enabled = true
command = "/usr/local/bin/bringyour"
args = ["mcp"]

The remote MCP exists so an agent can discover Bring Your AI and get local install commands without leaving the agent window. It does not receive the user's harness.

Buy lifetime access →

Sources: Axios on Anthropic capacity and Claude Code plan confusion; TechCrunch on Claude Code limits changing without clear user notice; Forbes on Claude Code limit complaints; Anthropic status page.

← back to bringyour.ai