Codex 26.608: Import Your Claude Code Config with One-Click Migration
TL;DR
OpenAI's Codex app 26.608 (June 9, 2026) ships a guided "Migrate to Codex" onboarding flow that imports six config types from Claude Code and Claude Cowork — including system prompts, custom skills, MCP server configurations, hooks, sub-agent settings, and 30 days of chat history. The same release revamped the plugins screen and expanded Settings search. Companion CLI 0.139.0 adds standalone web search inside code-execution mode, closing a notable capability gap.
v26.608
Codex app version that ships the Claude Code migration flow — released June 9, 2026
30 days
Chat history window imported from Claude Code or Claude Cowork during migration
v0.139.0
Codex CLI version adding standalone web search in code-execution mode — also June 9
6 config types
System prompts, custom skills, chat history, MCP servers, hooks, and sub-agent settings
A new migration flow targets Claude Code users directly. Codex app 26.608 introduces a guided "Migrate to Codex" onboarding experience that imports your existing configuration from Claude Code and Claude Cowork. This is distinct from the CLI desktop-handoff feature covered in yesterday's June 8 release — that update bridged the terminal and desktop surfaces; this one is specifically about lowering the cost of switching coding agents entirely.
Six config types transfer in the migration. The flow imports: system prompts, custom skills and shortcut commands, chat history from the past 30 days, MCP server configurations, hooks, and sub-agent settings. That covers the majority of the operational setup most teams accumulate in a coding agent over weeks of use — the kinds of configurations that historically made switching tools feel expensive even when a better option existed.
Permissions require a manual review after migrating. OpenAI explicitly recommends reviewing permissions after the import — the permission systems between Codex and Claude Code are not interchangeable, and configurations that carried over may not map cleanly to Codex's permission model. Operators should treat the migration as a starting point, not a finished port: audit what transferred, verify scope, and don't assume identical behavior. This caveat applies especially to hooks and sub-agent settings, where permission boundaries differ most between the two platforms. For a full breakdown of how Claude Code's permission model works before migrating, see the Cursor vs Claude Code comparison.
The plugins screen was also revamped. The same 26.608 release brings separate marketplace tabs, category filters, and keyboard navigation to the plugins screen. These are UX improvements rather than capability additions, but they matter for teams evaluating Codex's plugin ecosystem — easier discovery lowers the time to find and configure relevant plugins. Settings search was also expanded in this release.
CLI 0.139.0 adds web search inside code-execution mode. The companion CLI release (also June 9) ships standalone web search in code mode — the first native web-search capability in Codex's code-execution context. This includes web search from nested JavaScript tool calls, meaning agents running code can now reach the web mid-execution without leaving the code-mode environment. Previously, web search required switching contexts. For teams building on the best AI coding tools for agentic workflows, this closes a gap that distinguished Codex from tools with more integrated search capabilities.
The competitive signal here is deliberate. Building a migration importer that specifically names Claude Code and Claude Cowork is not an incidental feature — it's OpenAI identifying Claude Code as the primary reference point for developers it wants to convert. The specificity of what transfers (MCP configs, hooks, sub-agents) signals that OpenAI understands how Claude Code users actually set up their environments. For teams currently evaluating coding agents, this materially lowers the cost of running a side-by-side trial: you don't need to rebuild your config from scratch to give Codex a fair test.
Why It Matters
OpenAI is actively reducing the switching cost from Claude Code to Codex. Building a named, guided migration importer for Claude Code and Claude Cowork configurations is a direct competitive move — it signals that OpenAI treats Claude Code as the benchmark coding agent it needs to convert users away from. The specificity of what transfers (MCP servers, hooks, sub-agents, 30 days of history) reflects a detailed understanding of how Claude Code teams are actually configured, not a generic settings dump. The permissions caveat matters operationally — teams should not assume migrated configs are production-ready without a deliberate review pass. Meanwhile, web search in code mode (CLI 0.139.0) closes a capability gap that previously favored alternatives with more integrated search. Together, these two June 9 updates give teams a lower-friction path to evaluating Codex without abandoning their existing Claude Code investment.
Who's Affected
- — Claude Code users evaluating alternatives — the migration flow now lets you import your full config setup (system prompts, MCP servers, hooks, skills, 30 days of history) into Codex without rebuilding from scratch; this is the lowest-friction trial path that has existed for Codex to date
- — Teams standardizing on a coding agent — the existence of a named Claude Code import flow signals that Codex is actively competing for this segment; it's worth running a parallel evaluation now that the setup cost has dropped significantly
- — Developers who need web search inside code execution — CLI 0.139.0 adds the first native web-search capability in Codex's code mode, including from nested JavaScript tool calls; this changes what agentic code workflows can do mid-execution
- — Operators managing coding-agent switching costs — the migration importer covers the six config types most teams accumulate over time; factor the permissions-review step into your migration timeline, as the permission systems are not interchangeable
What To Do Now
- 1. Run the "Migrate to Codex" flow as a trial, not a commit — the importer gets your system prompts, skills, MCP servers, hooks, sub-agent settings, and 30 days of chat history into Codex in one pass, making a side-by-side evaluation feasible without rebuilding config from scratch
- 2. Review all permissions after migrating — OpenAI explicitly flags that Codex and Claude Code permission systems are not interchangeable; audit every imported hook and sub-agent setting before using the migrated config in any production or sensitive-access workflow
- 3. Test CLI 0.139.0 web search in code mode — if your agentic workflows require looking up current documentation, package versions, or live data during code execution, this is now available natively without a context switch; upgrade via your usual Codex CLI upgrade path
- 4. Treat the plugins screen revamp as a discovery pass — the new category filters and separate marketplace tabs in 26.608 make it faster to find relevant plugins; schedule time to review available plugins if you haven't evaluated the Codex plugin ecosystem recently
More on this topic — Best AI Coding Tools
Independent Review
Claude Code
Pricing, pros and cons, real-world verdict — no affiliate spin.
Read the Claude Code reviewMore from ToolNav News