Brooke Wright
Brooke Wright · @wright_mode
FREE GUIDE

Take your Claude setup anywhere

The 10-minute transfer that moves your instructions, connectors and skills into Codex — and lets you run both tools side by side.

Copy-paste ready10-minute setupBuilt by Brooke
Something went wrong. Please try again.

No spam. Unsubscribe anytime.

The 10-minute transfer that moves your whole Claude setup into Codex Jump to the transfer → Join the Membership
Wright Mode — Free Resource

The Claude → Codex Transfer Guide

Copy your entire Claude setup into Codex — instructions, connectors, skills and chats — without starting from scratch.

⏱ 10-minute setup🧰 No code required↔️ Works both directions📋 Copy-paste ready

What's inside

1The 10-minute transfer2What transfers (and what doesn't)3Run both, side by side

The 10-minute transfer

ChatGPT now has a built-in importer that detects your Claude setup and moves it across — no files, no code. Here's the exact path.

1

Open ChatGPT (desktop app) → Settings → Import

It's in the left sidebar under Personal. The page reads: "Bring setup, projects, and chats from other AI apps into ChatGPT."

2

It detects your Claude apps automatically

Under "Import from another AI app" you'll see Claude Code and Claude Cowork listed with an Import button next to each — it found them itself.

3

Choose what to bring over

Tick Tools & setup (settings, instructions, plugins, skills), Projects, and Chat sessions. Your existing Claude setup is not affected — this is a copy, not a move.

4

Optional: turn on autosync

"Keep imports in sync" automatically carries new and updated content across from then on. Leave it off if you just want a one-time copy.

Heads up: some projects won't import

Projects with an unsupported configuration get skipped (mine showed "5 projects can't be imported"). That's what the fallback prompt below is for.

The fallback: make Codex do the move itself

If the importer skips something — or you'd rather move things by hand — paste this into Codex and let it do the work:

I'm moving my setup from Claude Code to Codex. Do this for me: 1. Read my Claude instruction files — the global one at ~/.claude/CLAUDE.md and this project's CLAUDE.md — and copy their content into AGENTS.md files in the matching places (~/.codex/AGENTS.md for global, ./AGENTS.md for this project). Adapt anything that's Claude-specific so it makes sense for you. 2. List the MCP servers in my Claude configuration and add the same servers to my Codex config so my connectors work here too. 3. Copy my custom skills into your skills folder (~/.codex/skills/), and convert any Claude slash commands into skills — you don't support slash commands, so rebuild each one as a reusable skill instead. When you're done, show me a summary of everything you changed and anything you couldn't move.

What transfers (and what doesn't)

The reason this works: the two tools are built more alike than anyone admits.

🟢 Claude Code reads

  • CLAUDE.md — your instructions
  • MCP connectors
  • Skills folder
  • Slash commands

🔵 Codex reads

  • AGENTS.md — same file, different name
  • MCP connectors — same servers
  • Skills folder — same idea
  • No slash commands — rebuild as skills
Instructions — copy CLAUDE.md into AGENTS.md, done
Connectors — Codex runs MCP too, re-add once
Skills — move into ~/.codex/skills/
Projects & chats — via the importer
Slash commands — no direct equivalent
Claude-only file names — Codex won't read CLAUDE.md itself

The takeaway

Your AI setup isn't married to one tool. Instructions travel, connectors travel, skills travel — the work you've put into your setup comes with you.

Run both, side by side

This isn't a divorce. If you use VS Code, Claude Code and Codex can sit in the same editor at the same time — and while the frontier labs fight it out for your subscription, you get the best of both.

1

Install both extensions in VS Code

Claude Code and Codex each have a VS Code extension. They don't clash — each opens in its own panel.

2

Keep CLAUDE.md and AGENTS.md side by side

Same content in both files means both tools know your business, your stack, and your rules — whichever one you open.

3

Let them race

Give the same job to both for a week. You'll quickly learn which one you reach for — and you'll have an opinion based on your own work, not someone's YouTube video.

Don't pay twice for the same job

Running both is for finding your favourite — once you know, you only need one subscription doing the heavy lifting.

Ready to go deeper?

Take your skills to the next level with these resources.

Community + Training

Wright Mode Membership

Join a community of women entrepreneurs implementing AI and automation in their businesses. Live calls, templates, and ongoing support.

Learn more →
Workshop Replay

Claude Masterclass

Learn how to use Claude like a pro. From prompting fundamentals to building real workflows that save hours every week.

Watch now →
Next Level

Claude Code Masterclass

Go beyond the chat interface. Build automations, process data, and create tools with Claude Code — no developer experience needed.

Explore →