Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.213 Home All releases olderv2.1.212 v2.1.214newer
Claude Code v2.1.213

/import — Migrate Config from Other AI Coding Agents

What

A new /import slash command (and claude import CLI subcommand) scans for OpenAI Codex and Google Gemini CLI configuration and imports it into Claude Code — MCP servers, slash commands, subagents, skills, and instructions.

Usage
# From the terminal (interactive picker)
claude import                 # auto-detect Codex or Gemini
claude import codex           # Codex only
claude import gemini          # Gemini only
claude import --dry-run       # preview without writing
claude import --yes           # apply all user-level items without prompting

# From inside a Claude Code session
/import                       # scan and list what's importable
/import --yes                 # apply everything without the picker
/import --dry-run             # show what would be imported
Details
  • Detects Codex config at ~/.codex/config.toml and .codex/ (project-level)
  • Detects Gemini config at ~/.gemini/settings.json and .gemini/ (project-level)
  • Imports MCP servers, slash commands (skills), subagents, and system instructions
  • Project-level config from .codex/ or .gemini/ directories is listed but NOT auto-imported — anyone with repo write access could author those, so they must be reviewed manually
  • Shell-exec markers (!{…} in Gemini, !cmd`` in Claude Code) are flagged and require manual porting
  • Items with no automatic mapping generate a helper skill at skills/import-to-claude-code/ for follow-up review
  • Gemini extensions, project-level settings, and subdirectory-organized commands are listed as needing manual review
  • The --yes flag on claude -p (headless/scripted) applies the same import that the interactive picker would; on plain claude -p sessions without a terminal, it instructs users to run claude import from an interactive terminal instead
  • Codex permission mode default maps to defaultMode: auto in Claude Code; tool restrictions differ and are dropped with a warning
Evidence

CLI entry point (search for "claude import [codex|gemini] [--dry-run] [--yes]"), Gemini config support (search for ".gemini/settings.json"), Codex support (search for ".codex/config.toml")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.213 →