Import Without Replacing

Lesson 2 · Setup · ~10 minutes

Codex can import supported setup from other coding agents without changing or deleting the original. That makes import a low-risk way to test continuity rather than a migration commitment.

Your win

Bring selected Kiro or Claude conventions into Codex, then review the translation before relying on it.

What Maps Where

Existing itemCodex destination
Instruction filesAGENTS.md
Settingsconfig.toml
Skills and slash commandsCodex skills
MCP, hooks, subagentsEquivalent Codex configuration
Recent sessionsCodex threads

Use the Import Flow

  1. Open Codex app Settings → General → Import other agent setup.
  2. Choose Customize instead of importing everything blindly.
  3. Start with instructions, one useful skill, and required MCP servers.
  4. Review permission assumptions, environment variables, authentication, and argument placeholders.
  5. Open one imported project and run a harmless read-only task.
Do not assume equivalence

Hooks, command interpolation, permissions, and connection authentication can behave differently. Imported means translated, not verified.

Import in Risk Order

Import items in an order that makes failures easy to diagnose. Static guidance is easier to inspect than executable hooks or authenticated connections.

  1. Instructions: compare the generated AGENTS.md with the source guidance.
  2. Skills: verify their descriptions trigger only for the intended tasks.
  3. Settings: inspect model, sandbox, approval, and feature choices.
  4. MCP and plugins: reconnect authentication and review tool permissions.
  5. Hooks and subagents: test side effects in a disposable repository last.

Run a Post-Import Audit

QuestionEvidence
Did guidance land at the correct scope?Global versus repository file location
Can any imported tool mutate external state?Tool list and approval policy
Are credentials still available safely?Environment-variable names, never secret values
Do command placeholders still expand correctly?Harmless dry run with sample arguments
Rollback model

The original agent setup remains untouched. If an imported item behaves badly, disable or remove that Codex copy instead of changing the working Kiro or Claude setup.

Check Your Understanding

What is the safest first move when bringing an existing agent setup into Codex?
Correct. Customize the import and keep the source setup intact.
The importer translates supported items while leaving the original setup unchanged.

Do This Now

Open the import preview and record which three items would provide immediate value. Rank them by execution risk, identify each Codex destination, and write one harmless verification task for each item before completing the import.

Primary Source

Import to Codex documents supported items, destinations, and post-import checks.

Questions? Show me the proposed import list and I can help identify risky or redundant items.
← PreviousNext →