Codex CLI: Import Settings and Sessions from Cursor and Claude Code
CodexCodex CLI's /import command now supports migrating configuration from Cursor, in addition to the existing Claude Code support introduced earlier in 2026. The expanded command can pull in MCP servers, plugins, sessions, slash commands, and project-scoped memories, making it easier for developers switching tools to bring their existing setup with them. This lowers the switching cost for teams evaluating Codex against other AI coding agents.
Key Takeaways
- Codex CLI's
/importcommand now supports Cursor, expanding on its earlier Claude Code migration support. - The importer can bring over MCP servers, plugins, sessions, and slash commands, not just basic preferences.
- Plugin-defined commands are automatically migrated into Codex's skills system on install, so they keep working without rewrites.
- Migration is one-way only — changes in Codex do not sync back to the original tool.
- The feature lowers the switching cost for teams evaluating Codex against other AI coding agents.
/importonly surfaces items Codex determines are new or different, avoiding duplicate imports on repeat runs.
Sources & Mentions
3 external resources covering this update
One-Way Migration from Cursor and Claude Code
Codex CLI's /import slash command, first introduced to migrate settings from Claude Code, was expanded in version 0.145.0 to also support Cursor. Run from inside the Codex CLI TUI, /import scans a developer's existing configuration and surfaces items that have not yet been imported or that differ from what Codex already has.
What Gets Migrated
The expanded importer can bring over MCP servers, enabled plugins, past sessions, custom slash commands, and project-scoped memories. Notably, Codex also migrates plugin-defined commands into its own skills system on install, so that commands built for another tool keep working inside Codex without manual rewriting.
A One-Way Bridge
The migration is intentionally one-directional: changes made after importing into Codex do not propagate back to Cursor or Claude Code. This positions /import as an onboarding tool for developers trying or switching to Codex, rather than a way to keep multiple agents in sync.