Skip to content
Dustin's AI Lab
Go back

Moving from Claude Code to Codex: I Built a Skill to Handle It

Migrating an entire personal harness from Claude Code to Codex is not trivial — claude.md / agents.md, MCP, hooks, settings each need their own translation. I packaged the workflow as a Skill on GitHub. Plus a note on why I keep reaching for Codex these days.


The thing I actually got done this weekend was migrating my Claude Code personal environment over to Codex.

Honestly, I have been reaching for Codex more and more. Beyond the generous quota resets, GPT-5.5 has dropped that oily tone — work conversations feel grounded again. Meanwhile Opus 4.7 keeps making me want to slap it.

But moving an entire harness over is hard.

The pain points

What the Skill does

I packaged the migration into a Skill:

Repo: https://github.com/danyuchn/claude-codex-harness-sync

Claude Code → Codex migration Skill

A side gripe: Codex CLI still has gaps

After using Codex for a stretch, the most painful gap is the CLI — /rewind not being available is hard to forgive. On Claude Code, /rewind is daily survival. After migrating, the first time you make a wrong turn you realize there is no clean undo. Either git stash or rerun the whole conversation. Productivity hit is real.

Hoping OpenAI ships those CLI updates soon.

A small accident with image generation

While generating images, I noticed something: issuing image prompts directly inside Codex produces better results than having Claude Code hand them off to Codex.

Why? Because Claude tends to issue over-constrained prompts, while GPT-image-2 actually shines with fewer constraints — its creativity lives in the negative space.

The more layers of intermediation, the more the original intent gets “polished” away. Worth thinking about for any cross-agent task handoff, not just image generation.


Share this post on:

Previous Post
GPT-image-2 Wants Fewer Constraints — Plus a Consistency Drill
Next Post
You're mass-applying with AI. They're mass-screening with AI. Who wins?